Having two instances on the other gives you a "testing environment" for free. Update your author instance first, test if everything is still o.k., then update the public instance. On small projects that don't have a test or integration server this can be very helpful.
-will On 26.03.2012, at 15:28, Davide Montesin (via Magnolia Forums) wrote: > Thanks Will and Richard! > With two instances is even necessary to sync resources like ftl or jsp that > are changed. > At the same time, otherwise file system and templating data is not working > correctly. > > But I think is a goog idea to remain "standard" with two instances. If one > instance > is not a supported case, better to avoid it with custom programming. I have > not enought > skill to "change" magnolia. > > I try to work in direction two instances ... > > -- > Context is everything: > http://forum.magnolia-cms.com/forum/thread.html?threadId=1ecb3336-18a4-4dd8-a136-707b9ff32222 > > > ---------------------------------------------------------------- > For list details, see http://www.magnolia-cms.com/community/mailing-lists.html > Alternatively, use our forums: http://forum.magnolia-cms.com/ > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
