123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152 |
- .. _celery-installation:
- Installation
- ============
- You can install Celery either via the Python Package Index (PyPI)
- or from source.
- To install using `pip`,:
- .. code-block:: console
- $ pip install -U Celery
- To install using `easy_install`,:
- .. code-block:: console
- $ easy_install -U Celery
- .. _bundles:
- Bundles
- -------
- Celery also defines a group of bundles that can be used
- to install Celery and the dependencies for a given feature.
- You can specify these in your requirements or on the :command:`pip`
- command-line by using brackets. Multiple bundles can be specified by
- separating them by commas.
- .. code-block:: console
- $ pip install "celery[librabbitmq]"
- $ pip install "celery[librabbitmq,auth,msgpack]"
- The following bundles are available:
- Serializers
- ~~~~~~~~~~~
- :``celery[auth]``:
- for using the ``auth`` security serializer.
- :``celery[msgpack]``:
- for using the msgpack serializer.
- :``celery[yaml]``:
- for using the yaml serializer.
- Concurrency
- ~~~~~~~~~~~
- :``celery[eventlet]``:
- for using the :pypi:`eventlet` pool.
- :``celery[gevent]``:
- for using the :pypi:`gevent` pool.
- Transports and Backends
- ~~~~~~~~~~~~~~~~~~~~~~~
- :``celery[librabbitmq]``:
- for using the librabbitmq C library.
- :``celery[sqs]``:
- for using Amazon SQS as a message transport (*experimental*).
- :``celery[tblib``]
- for using the :setting:`task_remote_tracebacks` feature.
- :``celery[memcache]``:
- for using Memcached as a result backend (using :pypi:`pylibmc`)
- :``celery[pymemcache]``:
- for using Memcached as a result backend (pure-Python implementation).
- :``celery[cassandra]``:
- for using Apache Cassandra as a result backend with DataStax driver.
- :``celery[couchbase]``:
- for using Couchbase as a result backend.
- :``celery[elasticsearch]``:
- for using Elasticsearch as a result backend.
- :``celery[riak]``:
- for using Riak as a result backend.
- :``celery[zookeeper]``:
- for using Zookeeper as a message transport.
- :``celery[sqlalchemy]``:
- for using SQLAlchemy as a result backend (*supported*).
- :``celery[pyro]``:
- for using the Pyro4 message transport (*experimental*).
- :``celery[slmq]``:
- for using the SoftLayer Message Queue transport (*experimental*).
- :``celery[consul]``:
- for using the Consul.io Key/Value store as a message transport or result backend (*experimental*).
- .. _celery-installing-from-source:
- Downloading and installing from source
- --------------------------------------
- Download the latest version of Celery from
- http://pypi.python.org/pypi/celery/
- You can install it by doing the following,:
- .. code-block:: console
- $ tar xvfz celery-0.0.0.tar.gz
- $ cd celery-0.0.0
- $ python setup.py build
- # python setup.py install
- The last command must be executed as a privileged user if
- you are not currently using a virtualenv.
- .. _celery-installing-from-git:
- Using the development version
- -----------------------------
- With pip
- ~~~~~~~~
- The Celery development version also requires the development
- versions of :pypi:`kombu`, :pypi:`amqp`, :pypi:`billiard` and :pypi:`vine`.
- You can install the latest snapshot of these using the following
- pip commands:
- .. code-block:: console
- $ pip install https://github.com/celery/celery/zipball/master#egg=celery
- $ pip install https://github.com/celery/billiard/zipball/master#egg=billiard
- $ pip install https://github.com/celery/py-amqp/zipball/master#egg=amqp
- $ pip install https://github.com/celery/kombu/zipball/master#egg=kombu
- $ pip install https://github.com/celery/vine/zipball/master#egg=vine
- With git
- ~~~~~~~~
- Please the Contributing section.
|