Configure environment and secrets for Laravel · Ample Computer

Configure environment and secrets for Laravel

Configuration and secrets for a Laravel app on Ample. Verified on Laravel: an --env value delivered encrypted and reported as present without being echoed (secret=set). 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.

What it runs on

You need

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

  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=...
  1. 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 laravel patterns”
✓ configuration-secrets check from the example· http get/p/configuration-secrets → “see the pattern fixture checks”

Evidence

  1. November 6, 2026 · canary run
    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).

Tested examples

What it doesn’t cover