page:guides:symfony:schema changes

Apply Database Schema Changes for Symfony

Summary

Schema changes for a Symfony app on Ample. Verified on Symfony: a --release-command migration ran before activation and its marker was readable by the live app (migrated=release-ok). 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

Resource Requirements

Workflow 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.

Run Migrations as the Release Command

Ample runs the command before activation and fails the release if it exits non-zero; keep migrations idempotent.

ample deploy . --name  --public --release-command "python3 migrate.py"

Verify

Fetch the live URL and /p/migrated on the example; on failure read the build and runtime logs.

ample logs  --kind build

Success Checks

Limitations

Cost Estimate

Components

Note: Always-on monthly price of the tested sizes; apps auto-pause when idle. Buckets are allocation-priced per quota and not included.

Examples

Symfony Pattern Fixture

Evidence Summary

Last Verified At

2026-09-20T22:23:52Z

Unknowns

Formats

Next Actions