Read the statement by Michael Teeuw here.
MM with Docker
-
@schlomm Thanks, I understand, download new module files.
Ron R
-
@sdetweil Sam, I can’t believe how simple it was and I just over looked it in the docs. Thanks for being so patient with me.
-
@RonR you weren’t looking there, no biggie…
but your experience tells me I need to make it more clear…
will update the doc… -
I added this section to the doc
after the parms and before the 1st screenshot
-
@RonR hello. I did the same a while back and @sdetweil 's help and contribution is great!
I was trying to run two different MMs in two containers. The 2nd one was always seeing the same configs as the first(or something like that) even though though I was able to configure two different ports, one for each, but wasn’t able to run two different screen layouts.
This is what docker spooked be able to enable. Multiple parallel setups, then you just run a series of screens in kiosk mode and you can display the same setup on multiple locations and screens.
Maybe I’ll try again. I pasted about it here, and Sam did try to help. I gave up on it.
-
@OrangeMirror the current docker setup will only work for multiple instances
IF
you use the MM_CONFIG_FILE environment variable to run instances off different config files,
or
the MM_PORT env variable to override the port if using the same config.jsall the files will come from the ONE folder tree ~/magicmirror
so this means you would have to setup multiple entries in the compose.yaml to launch multiple instances (with the different config parms)
You have to change the container name too
this is because all the DATA used by the container is external (on docker host filesystem) and not IN the container
an example NOT using docker, but same idea here
https://docs.magicmirror.builders/configuration/introduction.html#advanced-configuration-and-frequently-asked-how-to-configure-examples
