Three named targets (app, horizon, scheduler) sharing a runtime-base
with PHP 8.3-FPM, opcache, redis, and pinned php-fpm pool config.
Composer + Node build stages are separate so vendor/ and public/build/
are baked into the runtime image.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Replaces the bare-metal `composer run dev` workflow with a fully
containerized 9-service stack orchestrated by docker compose. Single
command brings up the full app — three subdomains (marketing /
account / admin) reachable via Traefik with TLS, MariaDB + Valkey
+ Mailpit + Vite HMR + Horizon + scheduler all wired in.
Components:
- docker-compose.yml: traefik, app (php-fpm), web (nginx), mariadb,
valkey, mailpit, vite, horizon, scheduler.
- docker/: Dockerfiles, nginx config, entrypoint scripts.
- Makefile: convenience targets (up / down / logs / shell / migrate
/ seed / test / pint / etc).
- .env.docker.example: template for Docker-stack environment vars
(separate from website/.env so bare-metal devs aren't disrupted).
- website/vite.config.ts: server.host / origin / hmr / cors hooks
driven by VITE_HOST / VITE_ORIGIN / VITE_HMR_HOST so the same
config serves both bare-metal and Docker.
- website/bootstrap/app.php: redirectGuestsTo() now uses
request()->getScheme() so http: dev hosts don't get force-https
redirects.
- composer.json: drops laravel/sail (replaced by this stack).
- docs/superpowers/specs/2026-04-25-docker-compose-dev-environment-design.md:
full design spec.
Bare-metal `composer run dev` workflow stays usable for anyone who
prefers it — Docker stack reads .env.docker, doesn't fight
website/.env.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
