I like to chain them up instead such as
DEV AUTHOR -> DEV PUBLIC -> TEST AUTHOR -> PREVIEW PUBLIC -> LIVE (PUBLIC)
-> TEST PUBLIC
this allows us to show the customer a preview of the site and gives us a
test site to play with as well.
We refresh the test public from time to time with the content of the
preview public
Ruben
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]>
----------------------------------------------------------------
