I am currently getting to grips with buildout installs as I make the next version of our intranet.
Using buildout seems to be a good move towards a good disaster recovery in terms of being able to redeploy a site in the event of hardware failure (providing you have Data.fs backups of course). The only problem I have with it is when installing an egg that goes on to create problems, it's not necessarily clear as to how to get back to the previous install. I can look at the requires.txt in the EGG-INFO and determine what to delete but, of course, it isn't necessarily clear that the dependency has been installed for that particular product (if that makes sense). SVN would probably help, but I'm currently working/ developing on my local machine. Anyway, I digress... The production server that our intranet runs on is OSX and I'm currently developing the new site on my local MacBook but at some point I'll obviously be looking to go live with my dev and I would like some advice about doing this. The current 3.1.7 live build is configured with a zeo server & 4 zope clients (all on the same box) running behind Apache. Is it possible/ likely that I will be able to intsall a new 3.2.2 Plone zeo cluster (from the installer) onto the same box without affecting the current site? Then I can add my buildout file and fine tune as required before asking Apache to point to the new 3.2.2. Any thoughts? -- View this message in context: http://n2.nabble.com/Two-zeo-clusters-on-the-same-OSX-server...--tp3236531p3236531.html Sent from the Installation, Setup, Upgrades mailing list archive at Nabble.com. _______________________________________________ Setup mailing list [email protected] http://lists.plone.org/mailman/listinfo/setup
