Most of our customers run on maxcluster servers and therefore we use supervisord, which is brought by the setup. But one of our newer clients brought their own hosting and there was no supervisord, but systemd. So it was time to fiddle out, how to run Shopware queue workers and scheduled task with it.
supervisord and systemd are pretty similar – at least from the point of view of a PHP and Shopware developer ? . First we setup services, then we combine them into a group (it seems to be called „target“ in systemd ?) and voilá, done.
From this point on, everything I do is via a root account!
If you want to understand the details, I can recommend the blog articles by Benjamin Morel and Steven Rombauts who helped me a lot to make this work. Especially what the different lines do and why I need an @ in one of the filenames.
Systemd configurations living in /etc/systemd/system, so we create the two services there.
# Filename: shopware-message-consume@.service
[Unit]
Description=shopware messenger:consume
After=mysqld.service
StartLimitIntervalSec=0
PartOf=shopware.target
[Service]
Type=simple
Restart=always
RestartSec=1
User=www-data
ExecStart=/usr/bin/env php /var/www/bin/console messenger:consume --time-limit=300 --memory-limit=512M async default -v
[Install]
WantedBy=multi-user.target# Filename: shopware-scheduled-task.service
[Unit]
Description=shopware scheduled tasks
After=mysqld.service
StartLimitIntervalSec=0
PartOf=shopware.target
[Service]
Type=simple
Restart=always
RestartSec=1
User=www-data
ExecStart=/usr/bin/env php /var/www/bin/console scheduled-task:run --memory-limit=512M --time-limit=300 -v
[Install]
WantedBy=multi-user.target
# Filename: shopware.target
[Unit]
Description=shopware Worker
Wants=shopware-message-consume@1.service shopware-message-consume@2.service shopware-message-consume@3.service shopware-message-consume@4.service shopware-message-consume@5.service shopware-scheduled-task.service
[Install]
WantedBy=multi-user.targetOnce this is done, you need to reload the config of systemd and then you can start your service.
systemctl daemon-reload
systemctl start shopware.targetYou know the admin’s „duplicate“ button on products. Now the ticket says: „We need that, but from code — duplicate a product per sales channel, with adjusted name and its own product number.“ Or: „Campaign landing pages: clone this CMS page 20 times with different headlines.“ I’ve watched this get implemented as: load entity with […]
The requirement sounds harmless every time: „Log when a product price changes, with old and new value.“ Or: „When an order’s email changes, notify the old address.“ Or the audit-trail classic: „Who changed what, from what, to what?“ And every time, the naive implementation is the same sad shape: subscribe to product.written, load the entity […]
A code review scenario. A plugin adds a purchasePrice-style field to a custom entity — internal margin data. The review question: „Can the Store API read this?“ Followed by: „Can the Admin API write that computed field you recalculate in a subscriber?“ The answers, in the plugin at hand, were „yes“ and „yes, and then […]
