A skeleton for a Celery worker
Python Shell
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
buildout
conf
docs/api
plugins/basic_task
sources
Makefile
README.md
RELEASE
VERSION
buildout.cfg
buildout.deploy.cfg
buildout.devel.cfg
fabfile.cfg
fabfile.py

README.md

Overview

A Celery Python worker

Characteristics

  • automatic virtualenv management and requirements installation (type make)
  • automatic import of the tasks in the given namespace
  • creation of a Celery command (ie, celery XXXX) as well as a standalone script (ie, bin/XXXX).
  • separate development and production configurations. When you type make, we will use the development build process (buildout.devel.cfg) and settings, but a make rpm will use the build (buildout.deploy.cfg) for deployment on production machines.
  • project cleanup (type make distclean)
  • automatic Sphinx documentation (type make docs or make docs-pdf on the project root directory). It will discover any packages in the sources and add the corresponding files in the docs/api directory...
  • 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...
  • optional redis build and installation (inside the virtualenv)
  • basic fabric file, based on a config file (fabfile.cfg), for doing things like deploying RPMs, starting/stopping services, cleaning up logs on the remote machines, etc.

Usage

  • 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 buildout* scripts
  • add your code in the sources directory,
  • add your tasks in the plugins directory, and update the buildout/develop directories

FAQ

Can I change the Python version?

Set a different version on the Makefile with the SYS_PYTHON variable