What: Several deployment recipes in DEPLOYMENT.md run the app's production Docker target standalone and route external HTTP traffic straight to the container's exposed port, but that target only runs supervisord → php-fpm, which speaks FastCGI, not HTTP.
Where:
Dockerfile:87-94 (production stage) — only starts supervisord, which only runs php-fpm on port 9000; nginx is a separate container only wired up in docker-compose.yml, not present in this imageDEPLOYMENT.md:27-34 — docker run -p 80:9000 ...DEPLOYMENT.md:113-127 — Heroku recipe (ENV PORT=8080, sed -i 's/9000/$PORT/g')DEPLOYMENT.md:129-145 — Google Cloud Run recipeDEPLOYMENT.md:159-190 — AWS ECS recipe (containerPort: 9000)
Why it matters: Any of these recipes followed as written will receive raw HTTP requests at a port that only understands FastCGI — the deployments fail outright, not just misbehave. This affects every non-docker-compose deployment path documented in the file.
Suggested fix: Either document that these targets require an nginx (or other FastCGI-aware) reverse proxy/sidecar in front of php-fpm, or add a combined nginx+php-fpm build stage/target that these single-container platforms (Heroku, Cloud Run, ECS) can actually use directly.
What: Several deployment recipes in DEPLOYMENT.md run the app's
productionDocker target standalone and route external HTTP traffic straight to the container's exposed port, but that target only runssupervisord→php-fpm, which speaks FastCGI, not HTTP.Where:
Dockerfile:87-94(productionstage) — only startssupervisord, which only runsphp-fpmon port 9000; nginx is a separate container only wired up indocker-compose.yml, not present in this imageDEPLOYMENT.md:27-34—docker run -p 80:9000 ...DEPLOYMENT.md:113-127— Heroku recipe (ENV PORT=8080,sed -i 's/9000/$PORT/g')DEPLOYMENT.md:129-145— Google Cloud Run recipeDEPLOYMENT.md:159-190— AWS ECS recipe (containerPort: 9000)Why it matters: Any of these recipes followed as written will receive raw HTTP requests at a port that only understands FastCGI — the deployments fail outright, not just misbehave. This affects every non-docker-compose deployment path documented in the file.
Suggested fix: Either document that these targets require an nginx (or other FastCGI-aware) reverse proxy/sidecar in front of
php-fpm, or add a combined nginx+php-fpm build stage/target that these single-container platforms (Heroku, Cloud Run, ECS) can actually use directly.