-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tarek Ziadé wrote: > Hello > > We are happily using zc.buildout to deploy our Python softwares (mainly > zope) in production. > > The offline mode is very helpfull to create a media with a prepared buildout > to deploy the thing on a server that has no web access (this is most of the > time the case i guess) > > Now I am working on the best ways to prepare upgrades for the production and > I try to find a way to avoid recreating a big tarball again just for a few > changes. > > My guess is that a snapshot of the download-cache and eggs directory is > enough, so a diff can be made to "upgrade" a production server with a > tarball of the two directories and the new .cfg > > But I was wondering if someone had similar experiences already, and maybe a > simple, better way ? > > Thanks
I would avoid "upgrade in place" scenarios for production use: roll an entirely new deployment into a separate directory, use repozo to dump and reload the ZODB, bring up the new version, test, then switch the port numbers. Just my USD 0.02, Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHYBZQ+gerLs4ltQ4RAtWXAKDLmOBq5ZcDFnVbMoknbAZW+cIXTgCgvZlo PFELpT7lPY87E0En4WGCOHI= =5FER -----END PGP SIGNATURE----- _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
