On 25-04-12 12:21, Reikje wrote:
> Hi, I am looking into buildout to deploy a django webapp and all it'sI have a production.cfg that extends buildout.cfg. I can then add extra
> dependencies. I find it quite useful even during development because it
> forces you to keep track of your dependencies. A question regarding some
> best practices. Lets say I have buildout.cfg and setup.py in my project
> root and checked in into SCM. My webapp is listed under develop in
> buildout.cfg. While this is great, during deployment this is probably
> not what you want because you wanna lock the version of your source
> code. I want to do a git revision checkout to archive this. So i guess I
> need to maintain two different buildout.cfg files, one for development
> and one for deployment. How can this be organized to avoid DRY?
parts ("set up a supervisord to run gunicorn") of modify settings in
existing ones ("use port 10026 instead of 8000").
I get to keep it pretty DRY that way.
Note that I make proper packages out of my development apps and stick
For hints on getting your own packages up on a pypi of your own:
> On a side note, what are the alternatives to buildout. Maybe there isBuildout provides two things:
> something even better :)
- Installation + isolation of python packages, just like the
- Add-on recipes for extra automation. Great for deployment. Generating
=> for handling everything *within* your project directory, nothing
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.