page:guides:laravel:configuration secrets

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.

Prerequisites

Workload

Configure environment and secrets

Framework

Laravel

Tested Configuration

Workflow 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.
    Command: ample deploy . --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.
    Command: ample logs --kind build

Examples

Success Checks

Limitations

Cost Estimate

Evidence Summary

Formats

Next Actions