Brent, Thanks for your quick response. To give some more perspective, all our templates are written in freemarker. Also, we do not have any java classes that back the templates (so far). This means, we can activate the templates and content without restarting the servers. If we used custom module for the deploys, we would have to restart the server everytime. On the other hand, I do agree with you in some aspects. It does make perfect sense to deploy template and Jave code as part of a module. But if there were only templates that need to be deployed, I am not sure custom module would be the most efficient approach. Do you have a lot of of backing Java classes that your templates depend on? Does anyone else use the custom modules for deployments, where only template changes are made. Thanks Garima ________________________________
From: [email protected] [mailto:[email protected]] On Behalf Of Brent McArthur Sent: Sunday, November 15, 2009 5:50 PM To: Magnolia User-List Subject: [magnolia-user] RE: Deploying template files to production Hi Garima, Are you deploying your template changes as part of a standard Magnolia Module? To learn more about modules: 1. http://documentation.magnolia-cms.com/reference/custom-module.html 2. http://wiki.magnolia-cms.com/display/WIKI/Module+QuickStart We haven't come across this problem yet because we haven't made signiciant changes to our templates. However, we have planned for it. The plan is that if a template changes as part of a new version of our website module then we will migrate/fix all broken content as part of the module deployment process via the version handler. See http://wiki.magnolia-cms.com/display/WIKI/Handling+module+versions for more info on module versioning. We have a rule that we never deploy any changes to production environments unless those changes are packaged up and versioned appropriately in a standard module (mymodulev1.5.22.jar). You then deploy the module to all author and public instances. But of course you need to test the module in test environments first to ensure content is correctly fixed/deployed etc. Let me know if that helps. Cheers, Brent From: [email protected] [mailto:[email protected]] On Behalf Of Garima Parakh Sent: Saturday, 14 November 2009 1:51 AM To: Magnolia User-List Subject: [magnolia-user] Deploying template files to production 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]> ---------------------------------------------------------------- ________________________________ ---------------------------------------------------------------- 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]> ----------------------------------------------------------------
