Horizon and Task Scheduler in 1 Container Service

[eleonorsomosot]

Hi, we are trying to build 1 container service that will run Horizon and Task Scheduler, so that we can build only 1 ECS instance for it. Is there anyone who can help me navigate how to implement this properly?

I tried to combine the horizon and schedule:work commands in a single script, referenced it into command, and combined the health check for both, in a single script as well. However, the container won't start.

[jaydrogers]

You would have to a custom "long running" S6 Service: https://github.com/just-containers/s6-overlay

It's quite advanced and I get a lot of questions on this, but I intend to release some content how to do this since I get asked about it quite often.

Unfortunately the S6 docs are the best I can offer now, but I hope this helps!

[eleonorsomosot]

Hi @jaydrogers, thanks for responding and giving instructions. Hopefully, we can get some content to guide us at your earliest convenience. It's true, s6-overlay is quite advanced for me, though.

Right now, I was able to do it by combining the two commands in the container service. However, I think "long running" doesn't work since at some point in time, Horizon becomes inactive.

[eleonorsomosot]

Hi @jaydrogers, I managed to make it work with s6-overlay. I appreciate your suggestion. I'm still hoping we'll get that content soon.

However, right now, I am trying to add Laravel Reverb the same way I did with Horizon and Scheduler, but since ServerSideUp is running on 8080, I configured it to run on a different port, and that's where I hit a wall again. Hoping to get some guidance about it, and please include Laravel Reverb in the forthcoming content. Thanks!

[jaydrogers]

Here's how we run it:

https://serversideup.net/open-source/docker-php/docs/laravel/laravel-reverb

By default, our docs show we're running it on 8000 (which I am pretty sure was the defaults from the Laravel docs?)