Deploying Laravel without hand-writing a queue worker config
Most of what’s annoying about hosting a real Laravel app isn’t Laravel’s fault, it’s that a typical host wants its own config file, its own queue-worker process definition, and its own copy of whatever .env.example already states. The actual information needed to run the app correctly already exists in the repo; the hosting step shouldn’t need to ask for it again.
continue reading here : https://railyard.run/blog/deploy-laravel/
RailyardDeploying Laravel without hand-writing a queue worker config · RailyardAPP_KEY, migrations, Horizon, Reverb, Octane — Railyard reads what's already in composer.json and .env.example instead of asking you to declare it twice.
commit b7d3517