buildout

I have a batch job that I need to run occasionally against my Plone instance. It needs access to the code in my Plone product and other Plone code and to query the catalog. I've included the script in my Plone product and currently run it via bin/instance run <path to script in eggs directory> Obviously if a new version of my product comes along I need to change the path to point to the new version of the egg. What I'd like to do is define any entry point for the script in my product's setup.py and then use the buildout recipe like zc.recipe.egg so that I can just run bin/myscript How do I do

I'm working on setting up a Zope Replicated Storage (ZRS) based deployment. I currently have two servers (east and west) west will be the primary east will be the secondary I haven't touched the west box yet . On the east box I've edited my buildout as follows (I had to pin plone.recipe.zeoserver to 1.2.6 because the zrs features didn't exist before version 1.2.6): [zeoserver] recipe = plone.recipe.zeoserver[zrs] replicate-from = ${hosts:zeoserver-west}:${ports:zeoserver-zrs} [versions] plone.recipe.zeoserver = 1.2.6 After running bin/buildout I try to start my cluster and the instances seem

I am trying to switch fully to buildout - but our development environment already has lot of stuff installed in /usr/lib/pythonxx/ How can I make sure that buildout doesn't use the libraries installed on the system already - eventually without virtualenv ? For example - how to avoid this behavior ? : > cat buildout.cfg [buildout] parts = django [django] recipe = zc.recipe.egg eggs = django interpreter = django >bin/django >>> import django >>> django <module 'django' from '/usr/lib/python2.6/site-packages/django/__init__.pyc'> >>> Is there anyway to force buildout NOT to use the eggs installed

I'm working on a buildout script that needs to install a distutils package on remote server. On PyPi there are 2 recipes for doing this collective.recipe.distutils 0.1 and zerokspot.recipe.distutils 0.1.1 . The later module a derivative of the former, and is a little more convenient then the first, but the both suffer from the same problem, which I will describe now. When bootstrap.py is executed, it downloads zc.buildout package and puts it into buildout's eggs directory. This gives ./bin/buildout access to zc.buildout code, but /usr/local/python does not know anything about zc.buildout at

i have set up buildout project (django to be specific) that has to run in old machine, it works fine in my local system with python 2.7. In production server it runs python 2.5 and i want to configure buildout that it would download and use 2.6, but only this project not system wide. So i assume it should use some sort of recipe, but witch and how? I cannot find one. I hope to achieve it only using buildout.cfg file.. Buildout specifically supports this scenario. Each part in a buildout can use it's own python interpreter, or you can set one python interpreter globally for all parts. This

I've got several python applications consisting of scripts/modules that should be packaged and deployed as RPMs. The trickier bit is that each application should be distributed along with all python module dependencies, and these should be used in preference to any that are installed system wide. The target hosts for some of these RPMs have limited network access, so the RPMs should contain everything needed to run the app, rather than downloading anything at deploy time. I've looked at packaging and distributing a virtualenv , but relocating a virtualenv doesn't seem to be well supported. I

I am trying to grasp a bit more of buildout with this tutorial , but unlike a tutorial, it seems like a cut and paste of presentation slides. I don't have a really clear idea of what the purpose of buildout is, and how it positions itself with scons and setuptools. Would you be so kind to provide details on these issues? Thanks! DisplacedAussie I quite like the Plone Buildout Tutorial . It gives a reasonable overview of how it all works and the ways in which you can extend a simple buildout file. Here is the new link to Plone Buildout Tutorial . The most useful resource that I found so far are