Using supervisor for laravel queue worker

[insign]

In order to avoid mess with the image, what is the best way to configure a supervisor for laravel queue worker

[shinsenter]

@insign
I think you can use cron jobs
https://github.com/shinsenter/php?tab=readme-ov-file#using-cron-jobs

[insign]

I'm considering change the supervisor env command since I'll use the same image but start a exclusive container for the worker, any objection in your opinion?

[shinsenter]

@insign

Yes, I think that's also a viable option if you have the resources to run multiple containers for your project.

[insign]

Can I set a custom supervisor file?

[shinsenter]

@insign

Yes, although I haven't documented it in detail, my Docker images containing the web server use s6-overlay to act as a supervisor for processes.

I've also created a wrapper command s6-service to quickly set up a service using s6-overlay.

Here is an example of how to create a service in your Dockerfile:

# create s6-overlay services
if has-cmd s6-service; then
    s6-service laravel-queue longrun '#!/usr/bin/env sh
export APP_PATH="$(app-path)"
export APP_ROOT="$(app-root)"
cd $APP_PATH && exec php $APP_PATH/artisan queue:work
'
fi