Dylan Jay, on 2008-09-11: > Yuri wrote: >> Maurits van Rees ha scritto: >>> David Bain, on 2008-09-03: >>>> Perhaps I'm misreading the vanrees.org blog, but it seems to imply >>>> that eggs you develop yourself go into the src/ directory, even when >>>> they are production eggs. >>> >>> Partly. The eggs you develop yourself indeed go in the src/ dir. But >>> the stable.cfg that will be used in production (extended by >>> production.cfg) will not mention those development eggs. >>> >>> For each development egg an official egg is made (on the cheese shop >>> or on an internal egg server). Production uses those eggs. >> >> A server only for the purpouse to download a piece of software developed >> locally? This is a good practice in a multideveloper context, but is it >> ok to force it? I would create a custom/ directory to store stable eggs >> in production mode. Or do I miss something? :) > > I agree. can't an local directory be the index? like just use a file:// > stype url. Running a local pypi seems overkill for single instance sites.
Sure, file:///something works too. But if machine A has your instance and your eggs and machine A blows up, you will have a harder time setting up the instance again at machine B. > btw, I am ashamed to say I do use src dir for production using > svn-develop to pull down the code. but I know I should be using a better > release process. To make this a bit more robust, you can keep a record of what you are doing in your buildout. A simple HISTORY.txt file like this can already help: - 11 September 2008: did an svn up. Revision number is 800 - 9 September 2008: did an svn up. Revision number is 750 Then when after the update of 11 September you notice something is wrong, you can revert to revision 750 and have a working production site again, without having to first guess what would be a good revision to revert back to. -- 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
