# Apply database schema changes for Laravel

Schema changes for a Laravel app on Ample. Verified on Laravel: 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, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 template.

## What it runs on

- [Computeverified](/content/discover/primitive/compute/index.html)  
  Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [Postgresverified](/content/discover/primitive/postgres/index.html)  
  Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

## You need

- 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)
- A PostgreSQL driver reading DATABASE_URL at runtime
- An Ample account token with servers:write, databases:read

## 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. **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 <app-name> --public --release-command "python3 migrate.py"
   ```

3. **Verify.** Fetch the live URL and /p/migrated 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”  
✓ migrated check from the example· http get/p/migrated → “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: a --release-command migration ran before activation and its marker was readable by the live app (migrated=release-ok).

## Tested examples

- **Laravel pattern fixture.** Verified schema changes on Laravel.

## What it doesn’t cover

- Verified on the php-8.5 template at s-1vcpu-1gb.
- Managed PostgreSQL 16 with pgvector.
