Starting the Laravel scheduler / cron from serversideup/docker-php image

[fideloper-fly]

Hi!

Sorry you’re catching us mid-transition on using this style of container thing.

I’ve gotten most of the documentation updated (but not all of it) in a branch that’s not merged to the docs yet.

For now, check out this post on how to set it up:

Full Stack Laravel Bytes Tutorial Supervisor not working

OK, here’s the “official” way to to run cron / queues in this new set. Note: I started from a fresh application, and ran fly launch (using the latest flyctl) to ensure I got the newest setup. That creates files .dockerignore, files in docker, Dockerfile and fly.toml. After that was up and running, I added the following based on the processes docs. Here’s the whole fly.toml: app = "red-sea-8756" kill_signal = "SIGINT" kill_timeout = 5 processes = [] [build] [build.args] NODE_VERSION = …

1. The recommended workflow sets you up to essentially run multiple instances of your application
2. But you can also do this within one container, making use of S6

Check out the post I linked, and a few under it that go into trying to use it as a single container.

I’ll be verifying the single-container (vm) approach documenting that as well as the recommended use of [processes] within the fly.toml config.