Configure environment and secrets for Laravel | Ample
INFRASTRUCTURE
What it needs
- Compute: verified (Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.)
PREREQUISITES
Before you start
- A Laravel project (composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 template)
- An Ample account token with servers:write
TESTED CONFIGURATION
Exactly what was tested
- install:
composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader - runtime:
php - size:
s-1vcpu-1gb - start:
frankenphp php-server --listen :$PORT --root public - template:
php-8.5
STEP BY STEP
How to do it
- 1
Build and start
composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 template; the server must bind 0.0.0.0 on PORT.
- 2
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=...
- 3
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
EXAMPLES
Tested examples
- Laravel pattern fixture (
tests/deploy-canaries/laravel-patterns): Verified configuration and secrets on Laravel.
SUCCESS CHECKS
How to know it worked
- app responds on its public URL (
/on the live URL, expect ample canary laravel patterns) - configuration-secrets check from the example (
/p/configuration-secretson the live URL, expect see the pattern fixture checks)
LIMITATIONS
Know the limits
- Verified on the php-8.5 template at s-1vcpu-1gb; other sizes and Laravel major versions are not verified.
- Region, compliance attestations and request-duration limits are unknown and not claimed.
COST
Cost estimate
Estimated 5.00 USD per month (size prices from pricing.toml at build revision a1b8c38919e59cd035ebabaced73cf84ece24371).
- app server x1
s-1vcpu-1gb: 5.00 USD
Always-on monthly price of the tested sizes; apps auto-pause when idle. Buckets are allocation-priced per quota and not included.
EVIDENCE
Verification evidence
- canary_run on 2026-09-20T20:36:21Z at revision
118ad1c6d7d23d4c2ce069254bab9ec9d37cd57b-dirty (CLI 118ad1c): Laravel pattern fixture deployed on Ample (composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 template); for this guide: an --env value delivered encrypted and reported as present without being echoed (secret=set). (expires 2027-03-19T20:36:21Z)
EXECUTION
Execution binding
MCP tool ample_deploy (registry mcp:ample_deploy), schema hash 876465fce906da0c observed 2026-09-21T03:19:59.461917+00:00 at revision 49962bcade4f. Binding state at export: current. Required scopes: servers:write.
NEXT ACTIONS
Typed next actions
- Browse the catalog index (
GET /v1/catalogon the api origin; authentication not required, approval not required) - Search published recipes by intent, stack and constraints (
POST /v1/catalog/searchon the api origin; authentication not required, approval not required) - Prepare a side-effect-free deployment plan for an authorized project (
POST /v1/catalog/planon the api origin; authentication required, approval not required) - Read the existing agent authentication setup (
GET /mcp/setupon the api origin; authentication not required, approval not required) - Browse Laravel (
GET /v1/catalog/nodes/stack%3Aframework-laravelon the api origin; authentication not required, approval not required) - Browse Configure deployment (
GET /v1/catalog/nodes/intent%3Aconfigure-deploymenton the api origin; authentication not required, approval not required) - Browse Public web service (
GET /v1/catalog/nodes/pattern%3Apublic-web-serviceon the api origin; authentication not required, approval not required)
Actions describe possible next steps. They are typed data, not commands, and grant no permission. Public discovery never provisions anything; planning requires your own authenticated token and approval happens in your client.