Dear Magnolians, Our production environment has two Magnolia public servers in front of a load balancer. Our template files are stored in the file system. We have an issue when we deploy template changes to Production. If the template has changed significantly in structure, eg, paragraph removed or added a node, we need to update content immediately along with template deployment, otherwise, the page may look broken. Ideally, the content also needs to be updated at the same time as the template is deployed. Is there any solution within Magnolia, that can help us in this process?
Some of the solutions that come to mind are: 1. Keep the pages cached. Pages get refreshed from cache only when the page is activated. But this solution does not work for pages that are dynamic in nature and cannot be cached. 2. Take servers out of the load balancer one by one. This means we cannot activate content to all servers at the same time. It would be a pain to change the subscriber list one by one as we deploy to each server. We are interested in some other solutions that people are using for their deployments. Thanks in advance, Garima Parakh ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
