page:guides:symfony:deployment diagnostics

Diagnose Deployment Failures for Symfony

Deployment diagnostics for a Symfony app on Ample. Verified on Symfony: the same app deployed with a deliberate boot failure (CANARY_FAIL=boot): ample deploy exited 1 with a coded failure (health_check_failed when the process dies at boot, public_ingress_failed when the framework boots but every request answers 500) and the app's own error line was readable with ample logs --kind runtime, so the cause is read from the framework's output rather than guessed. Build and start: composer install --no-dev from composer.lock with Symfony Runtime's dotenv disabled (extra.runtime.disable_dotenv; .env never ships, its values arrive as encrypted env, and compile-time parameters such as DEFAULT_URI need a default), then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 template with APP_ENV=prod.

Prerequisites

A Symfony project (composer install --no-dev from composer.lock with Symfony Runtime's dotenv disabled (extra.runtime.disable_dotenv; .env never ships, its values arrive as encrypted env, and compile-time parameters such as DEFAULT_URI need a default), then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 template with APP_ENV=prod)
An Ample account token with servers:write

Workflow Steps

Read the failure code
Deploy is synchronous. Exit 1 with build_failed means the isolated build failed; health_check_failed means the app built but never answered on PORT (it crashed at boot or bound the wrong port); public_ingress_failed means it answered on PORT but the public URL returned an error status (a request handler or bootstrap failed); exit 2 means a required preflight action is blocking.
Read the build log
The last lines name the failing command and its output.
Command: ample logs --kind build
Read the runtime log
For health_check_failed the runtime log carries the Symfony process output: in the verified run the deliberate boot failure's own error line was there, followed by the platform's health-check verdict and the start command it ran.
Command: ample logs --kind runtime
Fix and redeploy once
Change the source, the environment or the command override, then run ample deploy again. Do not loop deploys to poll status; an unchanged redeploy is a no-op.
Verify
Fetch the live URL on the example; on failure read the build and runtime logs.
Command: ample logs --kind build

Success Checks

Failed deploy reports health_check_failed synchronously
Expect: ample deploy exits 1 with error.code health_check_failed
Runtime log carries the app's own error line
Expect: ample logs --kind runtime shows the framework's error output before the health-check verdict

Limitations

Verified on the php-8.5 template at s-1vcpu-1gb; other sizes and Symfony major versions are not verified.
Region, compliance attestations and request-duration limits are unknown and not claimed.

Cost Estimate

Currency: USD
Monthly Amount: 5.0
Basis: Size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty.
Components: App server, size: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.0.

Evidence Summary

Kind: canary_run
Summary: Symfony pattern fixture deployed on Ample with CANARY_FAIL=boot...(abbreviated for brevity)
Observed At: 2026-09-21T02:23:07Z
Expires At: 2027-03-20T02:23:07Z
Scope: checks...

Examples

Title: Symfony pattern fixture
Description: Verified deployment diagnostics on Symfony.
Source Reference: tests/deploy-canaries/symfony-patterns