@sdetweil said in MagicMirror problem:
Let’s try this
Change your config.js
address:”0.0.0.0”,
ipWhitelist:[],
Then
npm run server
Instead of npm start
Then use another system, phone to connect to that pi
http://pi-address:8080 geometry dash scratch
Thanks for your suggestion. I got it.
@Socrates note that without adding a parameter
The script does nothing. It only tests the ability to update the base MagicMirror
Update is two pass process
Test. Make no changes
Do. Apply the changes (with the parameter apply)
Many users have modified MagicMirror base code not knowing about the config and css file design. These changes block the ability to update normally
Over time they forget that they changed the files and what they actually changed. The force way to install is to wipe all changes, but now the result doesn’t work like it used to. Adding a lot of frustration.
@mumblebaj @KristjanESPERANTO @sdetweil
Thank you all for the information. I think I will stick with the way I already understand. setting up the docker and all seems like more work that is not in my wheelhouse. Interesting approach to the same end result.
@FrostByte as long as the change doesn’t affect a node_helper, which are only loaded at start time
the config.js os loaded as part of the web page
there is no notification it changed to the client browser
@blt791 it’s quite a lot of work. You can use the developers window sources tab to debug the code
Ctrl-shift-i, select the sources tab
Navigate in the left nav to your module and it’s source file
You can walk thru the code line by line if need be