Jahia Deployments

I am seeking tips from experienced Jahia users on three areas around
deployments:

1. Tracking Configuration Tweaks - 
Do any of you have a recommended process for keeping track of/backing up
all the files that get changed over time for configuring and tweaking
production servers (jahia.properties,
applicationcontext-basejahiaconfig.xml, etc)? 

2. Rollbacks - 
What methods are you all using for rolling back code changes? We have
all of our template and java integration code in version control, but
removing deployed files and redeploying seems error-prone. And a newly
untarred jahia install with a new integration jar each time seems a bit
heavy-handed. What are your experiences with rollbacks? Suggestions?

3. Deployments in a Clustered Environment - 
We have a working initial configuration of clustered nodes with
integrated templates and custom java, but are trying to work out the
best way to approach deployments for code changes/new templates. I found
a PDF, Jahia_Clustering_HOW-TO_v2.pdf for Jahia 4.0.5 that says some
templates/webapps deployment work needs to be done manually. In
particular, it recommends dropping in a jar/war on the fist server and
then manually copying the deployed files to the others servers in the
cluster. Does anyone know if Jahia 5.0.3 in a cluster will support
dropping in a jar on all servers? For those in a clustered environment,
what deployment process is working for you? Also is there a newer
version of this how-to document?

Thanks in advance for any thoughts, especially feedback from those who
have figured out successful processes to handle these scenarios!

Michelle Michael


_______________________________________________
dev_list mailing list
[email protected]
http://lists.jahia.org/cgi-bin/mailman/listinfo/dev_list