Here is your CLI tool to migrate or move all (or some) github issues from one repo to another!
Unlike some others, it also copies all the labels and all the tags properties (name, color, description).

[card:E3V3A/gh-missue]

This is very useful when your repo is full of crap and you wanna start from afresh but keep your issues.

PS. Require Ruby installed

@surger13 Did you read the text?
Make sure you have the latest version of node.js and npm installed.
– That’s exactly what it means.

I don’t have half installed as I like…

• [MMM-FlightsAbove] - Show what airplanes are buzzing around the sky above you
• [MMM-NOAA] - The old one, I like very much! (The now one not, too big headers ;)
• [MMM-crytocurrency] - With my own mods, keep me updated what is happening.

@sforsyth said in First mirror:

a trello todo list board (so my girlfriend and I can both update it from our phones if needs be),

Great mirror, look very neat.
Where is that Trello mod to be found?

Can you also give contact info to mirror company?

@ninjabreadman said in How to update the master branch?:

@PaulB First, make a backup of your install with cp -r ~/MagicMirror ~/MM-Backup.

Noo! Not a good idea if you’re running on a RPi with small SD card. That is a huge directory: du -sh ./ ~1.3GB, already for a quite small install. You might need that space for the update itself. Never good idea to max out your SD card.

Rather use tar, and try one of these:

cd ~
# remove `v` flag to avoid huge verbose output
tar --exclude={.git,node_modules} -zcvf MM_BAK.tgz ./MagicMirror
tar --exclude='node_modules' --exclude='.git' -zcvf MM_BAK.tgz ./MagicMirror

# This may require you to have the bash shell option globstar' set.
# Check with: 'shopt -s globstar'
tar --exclude='**/.git/*' --exclude='**/node_modules/*' -zcvf MM_BAK.tgz ./MagicMirror

This will avoid getting the huge node_modules and .git directories.
(You can always git init and reset your git origin url to git fetch from the resp directories if needed to re-instate.)

Just to say it…
It seem that many people having problems, are running something out dated.
Either: nodejs, npm, or pm2.

Because of the incredible dependency chain involved for node packages, I can only assume that using a newer versions of one package, will also require a newer version of the package depending on it, and possibly vice versa. Of course when things are working, it all beautiful, but it seem very easy that it doesn’t.

@NoNameRo

You guys should probaly do pm2 stop mm; pm2 kill to make sure it’s not running in the background.

Also, AFAIK, I think if you do git reset --hard you’d loose all your old config settings and other changes you’ve made?

@fabbr said in Ecobee:

Who wants to help me BETA test this?

Me too, where;s your repo?

You should post an issue to the github.

But, that said, I believe (I’ve never used this module) it keep track of changes to main MM config.js file, so if you change it, without restarting MM, this module will get confused. (make sure to use pm2 kill to avoid cached files.)

@aelmiri said in MMM-Assistant (updated) -- Your voice to the world!:

/home/pi/MagicMirror/modules/MMM-Assistant/node_modules/google-assistant/components/auth.js:18
throw new Error(‘Missing “keyFilePath” from config (should be where your JSON file is)’);

Ok, see solution from @drftg, above.

only file in assets is: config.txt

Of those files, you need to download one, one is generated from script, and another you need to create… Hmm, yes, I see the wiki doc definitely need updating… I’ll try to go through the procedure myself and update wiki after Easter.