that is why I like to chain them after each other (the dev public
activates to test author, etc). This way all configuration changes are
just activations (you can activate any configuration changes same as you
can activate an individual page. This way all the configurations stay
aligned and you have a visual control what has been published and what not.
Ruben
Matteo Pelucco wrote:
Ruben Reusser ha scritto:
I like to chain them up instead such as
DEV AUTHOR -> DEV PUBLIC -> TEST AUTHOR -> PREVIEW PUBLIC -> LIVE
(PUBLIC)
-> TEST PUBLIC
Hi Ruben,
Thanks for your reply.
We are going to keep almost the same configuration, but my question is
how do you keep aligned module configurations?
We have around 15 extra modules (developed by 3rd parts) and it will
be too hard to keep Magnolia instances manually aligned.
I've just done some little tests with Packager module, it seems a good
way to achieve this issue.
Is it possible also using activation? Are there side effects?
What do you (and other readers) think about it?
Matteo
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
