Mark Phillips, on 2008-09-01: > In the world of Plone 3, it seems I have to merge the buildout.cfg from > my development machine and the one on my production machine, taking care > to change only what needs to be changed - somewhat complicated by the > fact that the production server uses zeo and the development machine > uses a single instance of plone. Then, I copy over the src directory and > run bin/buildout.
You can use the same buildout directory (stored and tagged in svn) for development and deployment. Like Raphael said, you can use one cfg file for each situation. This is how we do it at Zest Software: http://vanrees.org/weblog/archive/2007/12/27/buildout-development-production-strategy > The merging of buildout.cfg files seems to be a very error-prone manual > process. You can make the two different cfg files look as much alike as you can so they are easy to compare. See: http://vanrees.org/weblog/archive/2008/07/08/versions-buildout BTW, those two weblog entries are from my brother Reinout, not from me. :-) -- Maurits van Rees | http://maurits.vanrees.org/ Work | http://zestsoftware.nl/ "This is your day, don't let them take it away." [Barlow Girl] _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
