A Python project template
- automatic virtualenv management and requirements installation (type
- separate development and production configurations. When you type
make, we will use the development build process (
buildout.devel.cfg), but a
make rpmwill use the build (
buildout.deploy.cfg) for deployment on production machines.
- project cleanup (type
- automatic Sphinx documentation (type
make docs-pdfon the project root directory). It will discover any packages in the
sourcesand add the corresponding files in the
- complete RPM packaging of the virtualenv, including the Python interpreter and
all the installed libs (just type
make rpm, and a nice rpm will appear the the top directory). This packaging method allows you to install any additional software in the virtualenv (ie,
nginx) and it will be nicely packaged in the RPM...
redisbuild and installation (inside the virtualenv)
fabricfile, based on a config file (
fabfile.cfg), for doing things like deploying RPMs, starting/stopping services, cleaning up logs on the remote machines, etc.
- search for all the occurrences of XXXX and replace them by your project name
- search for all the XXXX* files and rename them accordingly
- customize anything you want on the
- add your code in the
Can I change the Python version?
Set a different version on the
Makefile with the
How do you package things in the rpm?
The rpm is built by creating a virtualenv and installing all the eggs with the
virtualenv's easy_install. Any other artifact created by a compatible recipe
(ie, recipes that use the
Can I put some other stuff in the rpm?
Yes, just set the right
output attribute in your recipe.
How can I enable the redis build?
redis-config parts to the buildout.cfg/parts