Read the statement by Michael Teeuw here.
After 2.8 I'm having tons of issues. What are the steps from square 1 to get this working?
-
Obviously the folder was deleted when I ran the npm install in the MagicMirror folderNo it won’t be deleted.
Let’s start from scratch. U have the extra downloaded copy. Make THAT NAME MagicMirror, and npm install in that folder.
Start mm and we should be running.
Then we will copy over your extra modules, and config file
And work from there -
Alright. Now I have something else but a black screen for the first time in days:
“Magic Mirror - please create a config file”
What do you suggest now?
-
Obviously the folder was deleted when I ran the npm install in the MagicMirror folderNo it won’t be deleted.
Let’s start from scratch. U have the extra downloaded copy. Make THAT NAME MagicMirror, and npm install in that folder.
Start mm and we should be running.
Then we will copy over your extra modules, and config file
And work from there -
@sdetweil
That’s what I did. I have a fresh MagicMirror now. It is running but can’t find the config file (I haven’t copied config.js.sample to config.js yet). -
@maxheartrate you have to do that, copy the config
-
@maxheartrate I really want you to run my updated install script…if I can only find the topic with the link!
See the second post here
https://forum.magicmirror.builders/topic/10859/new-update-upgrade-script-ready-for-testing -
I am now using my original config.js and I am copying the modules one by one, then restarting Magic Mirror and checking if it still works.
I have got some stuff back up and running now. Thank so much up to this point.
-
I just did a reboot to see if MagicMirror survives it. :winking_face:
Since I ran your @sdetweil script in my time of desparation, pm2 now autostarts two instances of MagicMirror. One is MagicMirror and one my original mm.
Where do I edit this again? I forgot how I managed to do the autostart in the first place … sorry.
-
@maxheartrate just do
pm2 stop mm pm2 delete mm
