It has been suggested by others: activation.
Another way of solving this is having a module take care of it by
means of a version handler, which will go and (safely) modify the
configuration. By using module dependencies, you can control the order
of modules and make sure this one is the last.
-g
On Feb 20, 2009, at 9:59 AM, Matteo Pelucco wrote:
Dear Magnolians,
I'm facing with a distributed environment like this:
LIVE:
1 author - 2 public
TEST:
1 author - 1 public
DEV:
1 author - 1 public
What I see as my first large experience with Magnolia, is that it is
REALLY easy to "fork" the alignment of configuration as instance
number grows.
What do you do to manage this situation?
I'm going to build a "configuration checker", a sort of external
module which try to find differencies between configuration trees
over several instances...
M.
----------------------------------------------------------------
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]>
----------------------------------------------------------------
