Oh! Very good. I think I understand. It's starting to make sense. Thanks very much for the reply.
Sergey V. wrote: > > 1. Put your buildout configuration into svn. This actually includes only > the root folder, bootstrap.py and buildout.cfg. You will probably need > another config which includes settings which are deployment-specific, > let's call it deployment.cfg. > 2. Check everything out at the server: > svn co svn://mysvnserver.com/mycoolsite > 3. go to the mycoolsite folder and run bootstrap script: > python bootstrap.py > 4. Let buildout to do the rest of the job: > bin/buildout -c deployment.cfg > 5. Start the server: > bin/instance fg (or bin/instance start) > > If you made any ZODB changes at the dev site which you want to transfer to > the production, you will need to copy Data.fs too. > > The point is - generally you don't need to set up a Zope instance at the > server separately, buildout will create it for you. All you need is Python > of the right version. > > In the future if you need to update your production configuration all you > need is > > svn up > bin/buildout -c deployment.cfg > bin/instance restart > > > > afewtips.com wrote: >> >> Another part of the question is if I develop a site with a buildout, when >> I want to apply that configuration to a production server, do I have to >> use a buildout on the production server? >> It's not clear how go between enviornments. >> It looks like from the response and some other reading, that recreating >> the configuration has to be done in steps >> and cannot be processed in one step. >> > > -- View this message in context: http://n2.nabble.com/Moving-a-buildout-into-production-tp759400p780417.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
