How edit supervisor settings

[insign]

I'm not sure but I think since it uses s6-overlay supervisor file conf is different. I know that there is a supervisor env to set the command, but how can we tweak this file. I'm using laravel, and to make queues work with the laravel itself I need to run two containers one for laravel other for laravel queues. If there is a doc I would appreciate too.

[shinsenter]

@insign Would you mind sharing the exact command you're using on the second container to handle the Laravel queue processing?

I think one possible alternative is to use a per-minute crontab, as writen in the Laravel documentation.
https://laravel.com/docs/12.x/scheduling#running-the-scheduler

[insign]

@shinsenter SUPERVISOR_PHP_COMMAND="php artisan horizon" If I put it in the main container, the laravel itself stops working. BTW, Laravel Horizon is a better controller for queues.

[insign]

I want to edit it due to a weird but that the jobs are ran fine, marked as done but after some minutes que supervisor tries to run it again and since I marked the job run only once, it fails as "Max attempts to run" and the job was marked as successful now is marked and failed and keeps trying forever.

But since in that pov is a problem to me solve, I just asked in how can I try to tweak s6-overlay supervisor.

P.S: I don't know why SUPERVISOR_PHP_COMMAND breaks the main php thread, maybe it is used main/traditional php requests?

[shinsenter]

@insign

If I put it in the main container, the laravel itself stops working.

P.S: I don't know why SUPERVISOR_PHP_COMMAND breaks the main php thread, maybe it is used main/traditional php requests?

Yes, exactly - when you override the command using the SUPERVISOR_PHP_COMMAND environment variable, that command becomes the main process of the container. As a result, the web server to run Laravel will also be replaced. That’s the intended execution flow.

I think there’s no issue with the “one container – one process” design if you run the web server and Horizon in two separate containers.

[insign]

@shinsenter

I think there’s no issue with the “one container – one process” design if you run the web server and Horizon in two separate containers.

For that issue I just want to know how change or investigate the supervisor settings

[shinsenter]

@insign

The Laravel Docker image I provide uses s6-overlay as a supervisor to manage the startup of php-fpm and nginx processes. If you're interested in adding another s6-overlay service (like Laravel Horizon), you can refer to their following guideline and add a config file for your service. I believe adding this new service will be independent of the existing services included in the Docker images I provide.

Additionally, as I mentioned earlier, you can configure a crontab for Laravel Horizon using the ENABLE_CRONTAB and CRONTAB_SETTINGS environment variables. Another option is to use the autorun scripts feature to start Laravel Horizon in the background.

[insign]

Thanks I'll check these docs!

[shinsenter]

@insign I can only offer temporary suggestions like this because I don’t want to complicate the configuration of my Docker images. This would go against my original goal of providing simple, user-friendly Docker images.

[shinsenter]

@insign
I gave myself a little challenge and added a new environment variable LARAVEL_ENABLE_HORIZON to the Laravel Docker images. When this variable is set to 1, it will run an additional service for Laravel Horizon (assuming the Laravel Horizon package is already installed).

These Docker images with the new variable will be built within the next 24 hours and are available under the dev- tags. Feel free to give them a try if you’re interested.
http://hub.docker.com/r/shinsenter/laravel/tags?name=dev-

[shinsenter]

You can explore additional extended configurations for each specific project here.
https://github.com/shinsenter/php/tree/main/src/webapps

[shinsenter]

@insign
The Docker images for the dev- tags are currently being built.

I’ve also updated the README file for the Laravel Docker images — hopefully, it works as expected and is helpful to some extent.

[insign]

@shinsenter thank you for your support. I'm going try tomorrow and give you some feedback

[insign]

@shinsenter sorry for the delay, horizon worked very well, and since the configuration mostly comes from horizon.php, I only needed to set LARAVEL_ENABLE_HORIZON="1"

Thank you.

[shinsenter]

@insign
Thank you for your feedback.
This feature is also live on the shinsenter/laravel tags (not just the dev- ones).
Hope it's helpful to you!