maposmatic/support/systemd
Hartmut Holzgraefe e05711be43 add support for multiple render queues (Issue #91)
* maprenderingjob model now has a "queue" name column,
  defaulting to "default"
* methods dealing with the rendering queue now all either
  use the jobs queue column value if already available
  or have an additional optional "queue_name" parameter
  with default value "default"
* a systemd template service file was added to be able to start
  individual per-queue render services
* the progress bar in the map request detail view was finally
  fixed to show actual position-in-queue progress
2022-08-16 15:52:43 +00:00
..
README.md add support for multiple render queues (Issue #91) 2022-08-16 15:52:43 +00:00
maposmatic-render.service add support for multiple render queues (Issue #91) 2022-08-16 15:52:43 +00:00
maposmatic-render@.service add support for multiple render queues (Issue #91) 2022-08-16 15:52:43 +00:00

README.md

Copy both .service files to /etc/systemd/system and edit them to change the path to the wrapper.py script to the actual script location on your system.

The maposmatic-render.service takes render requests from the "default" queue.

You can start this service by simply invoking

systemctl start maposmatic-render

and enable it permanently using

systemctl enable maposmatic-render

Jobs from additional queues, like e.g. "api", can be rendered using the maposmatic-render@.service template. To start a service for a specific queue add the queue name after the @ sign, e.g.:

systemctl start maposmatic-render@api