index.html 12 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265
  1. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
  2. <html>
  3. <head>
  4. <meta charset="utf-8">
  5. <meta name="keywords" content="task queue, job queue, asynchronous, rabbitmq, amqp,
  6. redis, django, python, webhooks, queue, distributed">
  7. <meta name="description" content="open source distributed task queue" >
  8. <link rel="icon" type="image/png" href="favicon0.png">
  9. <meta name="viewport" content="width=500, user-scalable=no">
  10. <link rel="apple-touch-icon" href="favicon_64.png"/>
  11. <title>Celery - The Distributed Task Queue</title>
  12. <link rel="stylesheet" href="main0000.css"/>
  13. <link rel="stylesheet" href="trac0000.css"/>
  14. <script type="text/javascript">
  15. var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
  16. document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
  17. </script>
  18. <script type="text/javascript">
  19. try {
  20. var pageTracker = _gat._getTracker("UA-12986238-1");
  21. pageTracker._trackPageview();
  22. } catch(err) {}</script>
  23. <meta http-equiv="Content-Type" content="text/html;charset=utf-8">
  24. </head>
  25. <body>
  26. <div id="navbar">
  27. <div class="iStretch">
  28. <div class="link" id="current"><a href="index.html">Home</a></div>
  29. <div class="link"><a href="http://github.com/ask/celery">Code</a></div>
  30. <div class="link"><a href="http://celeryq.org/docs/">Documentation</a></div>
  31. <div class="link"><a href="community.html">Community</a></div>
  32. <div class="link"><a href="http://pypi.python.org/pypi/celery">Download</a></div>
  33. </div>
  34. </div>
  35. <div class="iStretch">
  36. <div id="topcontainer">
  37. <ul>
  38. <li>Background Processing
  39. <li>Distributed
  40. <li>Asynchronous/Synchronous
  41. <li>Concurrency
  42. <li>Periodic Tasks
  43. <li>Retries
  44. </ul>
  45. </div>
  46. <div id="contentcontainer">
  47. <div class="column">
  48. <h2>Distributed Task Queue</h2>
  49. <p> Celery is an asynchronous task queue/job queue based on distributed message passing.
  50. It is focused on real-time operation, but supports scheduling as well.</p>
  51. <p>The execution units, called tasks, are executed concurrently on a single or
  52. more worker servers. Tasks can execute asynchronously (in the background) or synchronously
  53. (wait until ready).</p>
  54. <p>Celery is already used in production to process millions of tasks a day.</p>
  55. <p>Celery is written in Python, but the protocol can be implemented in any
  56. language.
  57. It can also <a href="http://celeryq.org/docs/userguide/remote-tasks.html"
  58. >operate with other languages</a> using webhooks.</p>
  59. <p>The recommended message broker is <a href="http://rabbitmq.com/">RabbitMQ</a>,
  60. but support for <a href="http://redisdb.com/">Redis</a> and databases
  61. is also available.</p>
  62. Celery is easy to integrate with Django, Pylons and Flask, using
  63. the <a href="http://pypi.python.org/pypi/django-celery">django-celery</a>,
  64. <a href="http://pypi.python.org/pypi/celery-pylons">celery-pylons</a>
  65. and <a href="http://github.com/ask/flask-celery">flask-celery</a>add-on packages.
  66. <h3>Example</h3>
  67. <p>This is a simple task adding two numbers:</p>
  68. <div class="highlight"><pre><span class="kn">from</span> <span class="nn">celery.task</span> <span class="kn">import</span> <span class="n">task</span>
  69. <span class="nd">@task</span>
  70. <span class="k">def</span> <span class="nf">add</span><span class="p">(</span><span class="n">x</span><span class="p">,</span> <span class="n">y</span><span class="p">):</span>
  71. <span class="k">return</span> <span class="n">x</span> <span class="o">+</span> <span class="n">y</span>
  72. </pre></div>
  73. <p>You can execute the task in the background, or wait for it to
  74. finish:</p>
  75. <div class="highlight"><pre><span class="o">&gt;&gt;&gt;</span> <span class="n">result</span> <span class="o">=</span> <span class="n">add</span><span class="o">.</span><span class="n">delay</span><span class="p">(</span><span class="mi">8</span><span class="p">,</span> <span class="mi">8</span><span class="p">)</span>
  76. <span class="o">&gt;&gt;&gt;</span> <span class="n">result</span><span class="o">.</span><span class="n">wait</span><span class="p">()</span> <span class="c"># wait for and return the result</span>
  77. <span class="mi">16</span>
  78. </pre></div>
  79. <h3>Getting Started</h3>
  80. <ol>
  81. <li>Install celery by download or <code>pip install -U Celery</code></li>
  82. <li>Set up <a href="http://celeryq.org/docs/getting-started/broker-installation.html">RabbitMQ</a>
  83. or one of the <a href="http://celeryq.org/docs/tutorials/otherqueues.html">ghetto queue</a>
  84. solutions.
  85. <li>Select one of the following guides:
  86. <ul>
  87. <li><a
  88. href="http://celeryq.org/docs/getting-started/first-steps-with-celery.html">First steps with Python</a></li>
  89. <li><a href="http://celeryq.org/docs/django-celery/getting-started/first-steps-with-django.html">First steps with Django</a></li>
  90. </ul>
  91. </ol>
  92. <h3>Community</h3>
  93. <p>There is a <a href="http://groups.google.com/group/celery-users">mailing-list</a>
  94. available for general discussion.</p>
  95. <p>For those craving real, human interaction, there is also an IRC channel
  96. (<code>#celery</code> on <code>irc.freenode.net</code>).</p>
  97. <p>Finally, if you find a bug or would like to request a feature,
  98. please <a href="http://github.com/ask/celery/issues">submit an
  99. issue</a>.</p>
  100. <a name="donate"></a>
  101. <h3>Donate</h3>
  102. <p>
  103. <a href='http://www.pledgie.com/campaigns/8424'><img alt='Click here to lend your support to: celery and make a donation at www.pledgie.com !' src='http://www.pledgie.com/campaigns/8424.png?skin_name=chrome' border='0' /></a>
  104. </p>
  105. <p>Donations will be used to fund infrastructure and new features.</p>
  106. <p>
  107. You can <a href='http://www.pledgie.com/campaigns/8424'
  108. target='_new'>donate to the project</a> using PayPal.
  109. For other arrangements you can send an e-mail to
  110. <a href="mailto:donate@celeryproject">donate@celeryproject.org</a>.
  111. <div class="hidden">
  112. <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  113. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  114. </p>
  115. <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  116. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  117. </p>
  118. <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  119. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  120. </p>
  121. </div>
  122. </div>
  123. <div class="column side">
  124. <span class="newsitem">
  125. <h2>Celery 2.1.1 bugfix release</h2>
  126. <h4>By <a href="http://twitter.com/asksol">@asksol</a> on 2010-10-14.</h4>
  127. <p>All users are urged to upgrade. For a list of changes see the
  128. <a href="http://celeryq.org/docs/changelog.html">Changelog</a>.</p>
  129. <p>Users of Django must also upgrade to
  130. <a href="http://pypi.python.org/pypi/django-celery">django-celery 2.1.1</a>.</p>
  131. </span>
  132. <span class="newsitem">
  133. <h2>Celery 2.1 released!</h2>
  134. <h4>By <a href="http://twitter.com/asksol">@asksol</a> on 2010-10-08.</h4>
  135. <p>This new version is now available at PyPI. Be sure to read the
  136. <a href="http://celeryq.org/docs/changelog.html">Changelog</a> before upgrading.</p>
  137. </span>
  138. <span class="newsitem">
  139. <h2>Celery 2.0 released!</h2>
  140. <h4>By <a href="http://twitter.com/asksol">@asksol</a> on 2010-07-02.</h4>
  141. <p>We're proud to announce the release of Celery 2.0. This version replaces
  142. the Django ORM with SQLAlchemy as the database result store. With this, Celery no
  143. longer depends on Django. Django integration is now available as a separate package
  144. called <a href="http://pypi.python.org/pypi/django-celery">django-celery</a>.
  145. </p>
  146. <p>In addition there are a lot of new features: a curses monitor, time
  147. limits, complex crontab expressions, callbacks, simplified routing,
  148. and more. Everything is detailed in the <a
  149. href="http://celeryq.org/docs/changelog.html#id1">Changelog</a>,
  150. so be sure to read it before upgrading.</p>
  151. </span>
  152. <span class="newsitem">
  153. <h2>Celery 1.0.6 released!</h2>
  154. <h4>By <a href="http://twitter.com/asksol">@asksol</a> on 2010-06-30.</h4>
  155. <p>RabbitMQ 1.8.0 came with stricter equivalence checks that broke the
  156. AMQP result backend, this release resolves this. If you've already used
  157. the AMQP backend you need to delete the previous declarations. For
  158. instructions please read the full
  159. <a href="http://celeryproject.org/docs/changelog.html">Changelog</a>.
  160. Download from <a href="http://pypi.python.org/pypi/celery/1.0.6">PyPI</a>,
  161. or simply install the upgrade using <code>pip install -U Celery==1.0.6</code>.
  162. <hr>
  163. </span>
  164. <span class="newsitem">
  165. <h2>Celery 1.0.5 released!</h2>
  166. <h4>By <a href="http://twitter.com/asksol">@asksol</a> on 2010-06-01.</h4>
  167. <p>This release contains some important bug fixes related to shutdown and
  168. broker connection loss, as well as some other minor fixes. Also
  169. AbortableTask has been added to contrib. Please read the full <a href="http://celeryproject.org/docs/changelog.html">Changelog</a>
  170. before you upgrade. Download from <a href="http://pypi.python.org/pypi/celery/1.0.5">PyPI</a>,
  171. or simply install the upgrade using <code>pip install -U Celery</code>.
  172. <hr>
  173. </span>
  174. <span class="newsitem">
  175. <h2>Celery 1.0.3 released!</h2>
  176. <h4>By <a href="http://twitter.com/asksol">@asksol</a> on 2010-05-15.</h4>
  177. <p>This release contains a drastic improvement in reliability and
  178. performance. Please read the full <a href="http://celeryproject.org/docs/changelog.html">Changelog</a>
  179. before you upgrade. Download from <a href="http://pypi.python.org/pypi/celery/1.0.3">PyPI</a>,
  180. or simply install the upgrade using <code>pip install -U Celery</code>.
  181. <hr>
  182. </span>
  183. <span class="newsitem">
  184. <h2>Celery 1.0.1 released!</h2>
  185. <h4>By <a href="http://twitter.com/asksol">@asksol</a> on 2010-03-20.</h4>
  186. <p>This is a bugfix release and has some important changes to the
  187. shutdown procedure. Also improved compatibility with Windows and Python
  188. 2.4. Read the full <a href="http://celeryproject.org/docs/changelog.html">Changelog</a>
  189. for more information. Download from <a
  190. href="http://pypi.python.org/pypi/celery/1.0.1">PyPI</a>,
  191. or simply install the upgrade using <code>pip install -U Celery</code>.
  192. <hr>
  193. </span>
  194. <span class="newsitem">
  195. <h2>Celery 1.0 released!</h2>
  196. <h4>By <a href="http://twitter.com/asksol">@asksol</a> on 2010-02-10</h4>
  197. <p>Celery 1.0 has finally been released! It is available on <a
  198. href="http://pypi.python.org/pypi/celery/1.0.0">PyPI</a> for
  199. downloading. You can also install it via <code>pip install
  200. Celery</code>. You can read the announcement <a href="http://celeryproject.org/celery_1.0_released.html">here</a>.
  201. <hr>
  202. </span>
  203. </div>
  204. <div style="clear:both"></div>
  205. </div>
  206. <div id="credits">
  207. <ul>
  208. <li>
  209. <strong>Copyright (c) 2009-2010</strong>
  210. <span><a href="http://twitter.com/asksol">Ask Solem</a> and
  211. <a href="http://github.com/ask/celery/blob/master/AUTHORS">contributors</a>.</span>
  212. </li>
  213. <li>
  214. <strong>Web Design</strong>
  215. <span><a href="http://www.helmersworks.com/">Jan Henrik Helmers</a></span>
  216. </li>
  217. </ul>
  218. </div>
  219. </div>
  220. </body>
  221. </html>
  222. <!-- This document saved from http://celeryproject.org/ -->