Read the statement by Michael Teeuw here.
I'm new. Trying to understand and have a few questions....
-
Then when I hit: http://ip:2222/configure I am greeted with this:
yes, a module problem I guess…
see the output of npm start (harder to see in docker)
there are no module standards, and no program checking, so MMM-Config tries to discover everything… in config and out… and sometimes it encounters something that is unable to be worked around
-
@noviceuser yes, latest MagicMirror requires nodejs v20.18.1
and node 18+ has fetch built in
-
@sdetweil Yes, looking at this, I’ve never built my own container like that. If it was a simple pull and then run it then that is one thing. I haven’t gone that far with Docker yet.
I’ll just have to find a machine that I can run this on. That is one good thing about docker is that I don’t have to dedicate an entire VM to the software on it.
-
@noviceuser MagicMirror will run anywhere…
windows, linux, mac,
my automated installed handles linux and mac
-
@noviceuser I just updated MMM-Config to depend on a certain version or higher to stop the fetch failure
-
note for native running, including windows
in 2.30 we added start commands for the different mgrs
seehttps://forum.magicmirror.builders/topic/19269/new-magicmirror-start-options-in-version-2-30-0
-
@sdetweil So where is your install script? If you linked it already I apologize I missed it.
-
-
@sdetweil Thank you. I will take a look.
I figure once I get a healthy install I can work with that and see how dumb I am to this whole thing. I think part of my problem was the old docker image just not working right. I may be closer than I believe I am.
-
@noviceuser i also have backup/restore scripts where you can replicate a saved environment to a new platform (not windows)
https://github.com/sdetweil/MagicMirror-backup-restore
I’m starting to think i should create a windows restore
