Read the statement by Michael Teeuw here.
MM Crashed twice. Time to abandon MM?
-
How then do I convert my existing MM to
serveronly
?All the instructions seem to be for making a
serveronly
MM from the start.Thanks.
-
@richard238 Just enter your MM directory (e.g.
cd Magicmirror
) and runnode serveronly
. That should be all. Don’t forget to whitelist the IP of your remote computer, which will display MM. -
Ok, I’ll try that, thank you.
How do I get it back if I want to?
And can I still VNC to the Pi desktop? -
Not sure since I don’t use the
node serveronly
in my setup but a simplectrl+c
might do the trick. Or you use pm2. Make a short script withnano mm_so.sh
and paste the following (make sure your MagicMirror directory is correct)cd ~/MagicMirror node serveronly
ctrl+x
followed by a confirmation withy
will save it. Then typechmod a+x mm_so.sh
.
If you have pm2 installed you can then just run it by typingpm2 start mm_so.sh
. You stop it again by just enteringpm2 stop mm_so
.Disclaimer: I haven’t tried any of the above and it might contain errors or be simply wrong. Just give it a try. It doesn’t break anything.
-
@richard238 - To supplement @MadScientist excellent post, VNC works regardless of the Magic Mirror process state.
The default installation of Magic Mirror via the script uses pm2 to run a script at
/home/pi/MagicMirror/run-start.sh
. You can follow the instructions above to create your own script to run Magic Mirror in serveronly mode and switch between the two as you see fit.pm2 stop MagicMirror pm2 start mm_so
and so on and so forth. Do keep in mind that running the MagicMirror process with the interface enabled includes the web server. So your options are 1) full magic mirror with web server, and 2) web server only.