We have two zope instances, ~/production and ~/preview. There's an
update-production.sh script that:
*.tgzfiles, fresh custom product svn checkout)
The difference between update-preview and update-production is that update-preview copies over the production Data.fs. This way you can always test your current development with the real data. This realistic test is just an ssh to the server and a call to the update-preview.sh script away.
We're using this approach at our new customer Philips (an internal, mostly PloneHelpCenter based, website). We're only two weeks into the project, but we've already got this production/preview approach in place. The customer is already adding content and site structure into the real production site. At the same time, we can test our additions with the real data in the preview system. If we need to migrate some content or so, this gives us an ideal way of ensuring that it works with the current data.
Some additional notes:
repozo.pyscript in the zope/bin directory.
update-production.shscript of course makes a backup before potentially messing up the production website :-)
Are the update-* shell scripts availale somewhere?
My name is Reinout van Rees and I work a lot with Python (programming language) and Django (website framework). I live in The Netherlands and I'm happily married to Annie van Rees-Kooiman.
Most of my website content is in my weblog. You can keep up to date by subscribing to the automatic feeds (for instance with Google reader):