Atomic Coolify+Laravel Deployment

Improving my self-hosted Laravel deployments.I updated a handful of Coolify-hosted Laravel apps recently to get zero-downtime updates. Gone are those few annoying seconds of “no server available” I had been living with during deployments! Old Layout Previously, I had configured each app with the following resources in Coolify’s UI: Standalone database service (MySQL or PostgreSQL) added via UI. Easy backups, doesn’t have to restart for a deployment. Standalone Redis service, again added via UI so it can persist independently. docker-compose stack for the web server, scheduler, and queue. (Also Horizon and Reverb in some cases.) The monolithic docker-compose stack is what needed to change: # docker-compose.yaml (old layout) # Coolify deploys this as one stack: # Stops all containers, rebuilds, and starts; downtime during that window. services: octane: build: context: . dockerfile: ./.docker/octane/Dockerfile command: ["php", "artisan", "octane:frankenphp"] volumes: -…