Browse Source

Removes support for Beanstalk

Ask Solem 8 years ago
parent
commit
d4b0bf6fe3

+ 34 - 40
README.rst

@@ -128,8 +128,7 @@ It supports...
 
     - **Message Transports**
 
-        - RabbitMQ_, Redis_,
-        - MongoDB_ (experimental), Amazon SQS (experimental),
+        - RabbitMQ_, Redis_, Amazon SQS
         - CouchDB_ (experimental), SQLAlchemy_ (experimental),
         - Django ORM (experimental), `IronMQ`_
         - and more...
@@ -141,7 +140,7 @@ It supports...
     - **Result Stores**
 
         - AMQP, Redis
-        - memcached, MongoDB
+        - memcached
         - SQLAlchemy, Django ORM
         - Apache Cassandra, IronCache, Elasticsearch
 
@@ -157,7 +156,6 @@ It supports...
 .. _RabbitMQ: http://rabbitmq.com
 .. _Redis: http://redis.io
 .. _MongoDB: http://mongodb.org
-.. _Beanstalk: http://kr.github.com/beanstalkd
 .. _CouchDB: http://couchdb.apache.org
 .. _SQLAlchemy: http://sqlalchemy.org
 .. _`IronMQ`: http://iron.io
@@ -235,9 +233,9 @@ 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 ``pip`` comand-line
-by using brackets.  Multiple bundles can be specified by separating them by
-commas.
+You can specify these in your requirements or on the ``pip``
+command-line by using brackets.  Multiple bundles can be specified by
+separating them by commas.
 ::
 
     $ pip install "celery[librabbitmq]"
@@ -249,86 +247,82 @@ The following bundles are available:
 Serializers
 ~~~~~~~~~~~
 
-:celery[auth]:
+:``celery[auth]``:
     for using the ``auth`` security serializer.
 
-:celery[msgpack]:
+:``celery[msgpack]``:
     for using the msgpack serializer.
 
-:celery[yaml]:
+:``celery[yaml]``:
     for using the yaml serializer.
 
 Concurrency
 ~~~~~~~~~~~
 
-:celery[eventlet]:
-    for using the eventlet pool.
+:``celery[eventlet]``:
+    for using the ``eventlet`` pool.
 
-:celery[gevent]:
-    for using the gevent pool.
+:``celery[gevent]``:
+    for using the ``gevent`` pool.
 
-:celery[threads]:
+:``celery[threads]``:
     for using the thread pool.
 
 Transports and Backends
 ~~~~~~~~~~~~~~~~~~~~~~~
 
-:celery[librabbitmq]:
+:``celery[librabbitmq]``:
     for using the librabbitmq C library.
 
-:celery[redis]:
+:``celery[redis]``:
     for using Redis as a message transport or as a result backend.
 
-:celery[mongodb]:
-    for using MongoDB as a message transport (*experimental*),
-    or as a result backend (*supported*).
-
-:celery[sqs]:
+:``celery[sqs]``:
     for using Amazon SQS as a message transport (*experimental*).
 
-:celery[tblib]
+:``celery[tblib``]
     for using the ``task_remote_tracebacks`` feature.
 
-:celery[memcache]:
-    for using memcached as a result backend (using pylibmc)
+:``celery[memcache]``:
+    for using Memcached as a result backend (using ``pylibmc``)
 
-:celery[pymemcache]:
-    for using memcached as a result backend (pure-python implementation).
+:``celery[pymemcache]``:
+    for using Memcached as a result backend (pure-Python implementation).
 
-:celery[cassandra]:
+:``celery[cassandra]``:
     for using Apache Cassandra as a result backend with DataStax driver.
 
-:celery[couchdb]:
+:``celery[couchdb]``:
     for using CouchDB as a message transport (*experimental*).
 
-:celery[couchbase]:
+:``celery[couchbase]``:
     for using Couchbase as a result backend.
 
-:celery[elasticsearch]
+:``celery[elasticsearch]``:
     for using Elasticsearch as a result backend.
 
-:celery[riak]:
+:``celery[riak]``:
     for using Riak as a result backend.
 
-:celery[beanstalk]:
-    for using Beanstalk as a message transport (*experimental*).
-
-:celery[zookeeper]:
+:``celery[zookeeper]``:
     for using Zookeeper as a message transport.
 
-:celery[zeromq]:
+:``celery[zeromq]``:
     for using ZeroMQ as a message transport (*experimental*).
 
-:celery[sqlalchemy]:
+:``celery[sqlalchemy]``:
     for using SQLAlchemy as a message transport (*experimental*),
     or as a result backend (*supported*).
 
-:celery[pyro]:
+:``celery[pyro]``:
     for using the Pyro4 message transport (*experimental*).
 
-:celery[slmq]:
+:``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

+ 1 - 1
docs/faq.rst

@@ -185,7 +185,7 @@ Do I have to use AMQP/RabbitMQ?
 **Answer**: No.
 
 Although using RabbitMQ is recommended you can also use Redis.  There are also
-experimental transports available such as Beanstalk, CouchDB, or using
+experimental transports available such as CouchDB, or using
 SQL databases. See :ref:`brokers` for more information.
 
 The experimental transports may have reliability problems and

+ 0 - 63
docs/getting-started/brokers/beanstalk.rst

@@ -1,63 +0,0 @@
-.. _broker-beanstalk:
-
-=================
- Using Beanstalk
-=================
-
-.. _broker-beanstalk-installation:
-
-.. admonition:: Out of order
-
-    The Beanstalk transport is currently not working well.
-
-    We are interested in contributions and donations that can go towards
-    improving this situation.
-
-
-
-Installation
-============
-
-For the Beanstalk support you have to install additional dependencies.
-You can install both Celery and these dependencies in one go using
-the ``celery[beanstalk]`` :ref:`bundle <bundles>`:
-
-.. code-block:: console
-
-    $ pip install -U celery[beanstalk]
-
-.. _broker-beanstalk-configuration:
-
-Configuration
-=============
-
-Configuration is easy, set the transport, and configure the location of
-your Beanstalk database::
-
-    broker_url = 'beanstalk://localhost:11300'
-
-Where the URL is in the format of::
-
-    beanstalk://hostname:port
-
-The host name will default to ``localhost`` and the port to 11300,
-and so they are optional.
-
-.. _beanstalk-results-configuration:
-
-Results
--------
-
-Using Beanstalk to store task state and results is currently **not supported**.
-
-.. _broker-beanstalk-limitations:
-
-Limitations
-===========
-
-The Beanstalk message transport does not currently support:
-
-    * Remote control commands (:program:`celery control`,
-      :program:`celery inspect`, broadcast)
-    * Authentication
-

+ 0 - 5
docs/getting-started/brokers/index.rst

@@ -30,7 +30,6 @@ Experimental Transports
     django
     sqs
     couchdb
-    beanstalk
     ironmq
 
 .. _broker-overview:
@@ -49,10 +48,6 @@ individual transport (see :ref:`broker_toc`).
 +---------------+--------------+----------------+--------------------+
 | *Redis*       | Stable       | Yes            | Yes                |
 +---------------+--------------+----------------+--------------------+
-| *Mongo DB*    | Experimental | Yes            | Yes                |
-+---------------+--------------+----------------+--------------------+
-| *Beanstalk*   | Experimental | No             | No                 |
-+---------------+--------------+----------------+--------------------+
 | *Amazon SQS*  | Experimental | No             | No                 |
 +---------------+--------------+----------------+--------------------+
 | *Couch DB*    | Experimental | No             | No                 |

+ 0 - 3
docs/includes/installation.txt

@@ -98,9 +98,6 @@ Transports and Backends
 :``celery[riak]``:
     for using Riak as a result backend.
 
-:``celery[beanstalk]``:
-    for using Beanstalk as a message transport (*experimental*).
-
 :``celery[zookeeper]``:
     for using Zookeeper as a message transport.
 

+ 0 - 1
docs/includes/introduction.txt

@@ -148,7 +148,6 @@ It supports…
 .. _RabbitMQ: http://rabbitmq.com
 .. _Redis: http://redis.io
 .. _MongoDB: http://mongodb.org
-.. _Beanstalk: http://kr.github.com/beanstalkd
 .. _CouchDB: http://couchdb.apache.org
 .. _SQLAlchemy: http://sqlalchemy.org
 .. _`IronMQ`: http://iron.io

+ 1 - 1
docs/userguide/calling.rst

@@ -500,4 +500,4 @@ AMQP's full routing capabilities. Interested parties may read the
 
     A number between `0` and `255`, where `255` is the highest priority.
 
-    Supported by: RabbitMQ, Redis (priority reversed, 0 is highest), Beanstalk
+    Supported by: RabbitMQ, Redis (priority reversed, 0 is highest).