Hello —
I work at a company that is using MODX for their main website. We are a fairly sizable company and have many hosting security requirements.
Initially this site was created by installing MODX on three different servers (dev, stage, prod) and once updates passed QA for each environment would be dragged-and-dropped up to the next environment via FTP.
We quickly realized this is dumb and bad.
We saw that MODX can handle 3 different environments. This is awesome because we won't need three separate stand-alone instances of MODX. But one of the drawbacks of this is that we'd have to have one database that controls all three environments. Hosting did not like this at all and viewed it as a major security flaw. They said they were open to the idea of having one MODX instance control and work with all three environments (dev, stage, prod) but only if each environment could be attached to a separate database.
How can this be done? I'm still rather new to MODX so some of my wording or explanations may be amateur, so don't hesitate to ask for clarification.
Bottomline: Our goal is to have one MODX instance so we only have to have one username/password login. We can use MODX to transfer things between environments. Each environment has it's own independent database rather than a shared one. (I've been using this as reference:
http://rtfm.modx.com/display/revolution20/Contexts).
Any help would be
greatly appreciated.
