Configure environment and secrets for Symfony · Ample Computer
Configure environment and secrets for Symfony
Configuration and secrets for a Symfony app on Ample. Verified on Symfony: an --env value delivered encrypted and reported as present without being echoed (secret=set). 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.
Verified November 6, 2026
What it runs on
- Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.
You need
- 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
Exact tested configuration
- install composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader
- runtime php
- sizes 1vcpu-1gb
- start frankenphp php-server --listen :$PORT --root public
- template php-8.5
Steps
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; the server must bind 0.0.0.0 on PORT.
Pass values on deploy. Use --env KEY=value (repeatable) or --env-file; values are encrypted at rest and reused on redeploys. Declare names only in ample.toml.
$ ample deploy . --name <app-name> --public --env MY_SECRET=...Verify. Fetch the live URL and /p/configuration-secrets on the example; on failure read the build and runtime logs.
$ ample logs <deployment_id> --kind build
How it was checked
✓ app responds on its public URL· http get/ → “ample canary symfony patterns”
✓ configuration-secrets check from the example· http get/p/configuration-secrets → “see the pattern fixture checks”
Evidence
- November 6, 2026 · canary run
Symfony pattern fixture deployed on Ample (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); for this guide: an --env value delivered encrypted and reported as present without being echoed (secret=set).
Tested examples
- Symfony pattern fixture. Verified configuration and secrets on Symfony.
What it doesn’t cover
- Verified on the php-8.5 template at s-1vcpu-1gb.