Mercurial > kallithea
view docs/index.rst @ 8829:01cb988e82a5
celery: celery-run should only initialize app and sqlalchemy after workers have been forked
If app and SqlAlchemy were initialized before launching celery, the forked
workers would inherit the database connection ... and that doesn't work.
This could be handled by disposing the engine after forking the worker or
before each task ... but it remains unnecessary and wrong to initialize the
engine early when it isn't used, and then fork it.
author | Mads Kiilerich <mads@kiilerich.com> |
---|---|
date | Fri, 01 Jan 2021 18:04:16 +0100 |
parents | a3f649baa016 |
children |
line wrap: on
line source
.. _index: ####################### Kallithea Documentation ####################### * :ref:`genindex` * :ref:`search` Readme ****** .. toctree:: :maxdepth: 1 readme Administrator guide ******************* **Installation and upgrade** .. toctree:: :maxdepth: 1 overview installation installation_win installation_win_old installation_iis installation_puppet upgrade **Setup and configuration** .. toctree:: :maxdepth: 1 setup administrator_guide/auth administrator_guide/vcs_setup usage/email usage/customization **Maintenance** .. toctree:: :maxdepth: 1 usage/backup usage/performance usage/debugging usage/troubleshooting User guide ********** .. toctree:: :maxdepth: 1 usage/general usage/vcs_notes usage/statistics api/api Developer guide *************** .. toctree:: :maxdepth: 1 contributing dev/i18n dev/dbmigrations .. _python: http://www.python.org/ .. _django: http://www.djangoproject.com/ .. _mercurial: https://www.mercurial-scm.org/ .. _git: http://git-scm.com/ .. _celery: http://celeryproject.org/ .. _Sphinx: http://sphinx.pocoo.org/ .. _vcs: http://pypi.python.org/pypi/vcs