Multiple server instances -- one server and multiple config files, or multiple Docker instances?
Hopefully this is a quick question… If I wanted to have multiple instances of the MM server (so one can serve out one kind of web page; the second serves out a different web page; etc) on a single box, is there a right or wrong way to do this?
Searching the forums, I see some old discussion about creating three sets of config files then (presumably) having three instances of the server, each one using its own config file.
Given that Docker has come on the scene relatively recently, would it make more sense to have three Docker sessions and one MM server per Docker session (so that scripts and such wouldn’t have to be copied and modified)…?
@js999 u can install the mm code in separate folders too
then , like docker, the configs are unique files
u still need a unique port per instance
rin npm start server
karsten13 last edited by
you can do it with or without docker, thats your choice.
With docker you have to use different
config.jsfiles, they can be placed in the same folder and must be mapped into the right container.
You could use only one
modulesfolder for all instances by installing all modules there.
Updating the core is done by using a new docker image (same for all instances).
modules-folder may also could be established with the classic setup, you could use symlinks from a central place into the
modulesfolder of the several instances (never tested this!).