Skip to content

[Scheduler] Add some pointers regarding worker processes deployment #20439

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 10, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions scheduler.rst
Original file line number Diff line number Diff line change
Expand Up @@ -818,6 +818,14 @@ the Messenger component:
.. image:: /_images/components/scheduler/generate_consume.png
:alt: Symfony Scheduler - generate and consume

.. tip::

Depending on your deployment scenario, instead of manually executing this
Messenger worker process, you might want to run it with cron, supervisor or systemd,
and ensure workers are running at all times. Check out the `Deploying to Production`_
section of the Messenger component documentation.


Creating a Consumer Programmatically
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Expand Down Expand Up @@ -981,6 +989,7 @@ helping you identify those messages when needed.
to redispatched messages was introduced in Symfony 6.4.

.. _`MakerBundle`: https://symfony.com/doc/current/bundles/SymfonyMakerBundle/index.html
.. _`Deploying to Production`: https://symfony.com/doc/current/messenger.html#deploying-to-production
.. _`Memoizing`: https://en.wikipedia.org/wiki/Memoization
.. _`cron command-line utility`: https://en.wikipedia.org/wiki/Cron
.. _`crontab.guru website`: https://crontab.guru/
Expand Down
Loading