# Apply database schema changes for Quarkus

## Summary

Schema changes for a Quarkus app on Ample. Verified on Quarkus: a --release-command migration ran before activation and its marker was readable by the live app (migrated=release-ok). Build and start: `./mvnw -q -DskipTests package` producing one uber-jar (`quarkus.package.jar.type=uber-jar`), then `java -jar` on the jvm-21 template (Temurin JDK 21) with `quarkus.http.port` read from `PORT`.

## Infrastructure requirements

- 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.)
- Postgres: verified (Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no `DATABASE_URL` is supplied.)

## Prerequisites

- A Quarkus project (`./mvnw -q -DskipTests package` producing one uber-jar (`quarkus.package.jar.type=uber-jar`), then `java -jar` on the jvm-21 template (Temurin JDK 21) with `quarkus.http.port` read from `PORT`)
- A PostgreSQL driver reading `DATABASE_URL` at runtime
- An Ample account token with `servers:write`, `databases:read`

## Exact tested configuration

- template: `jvm-21`
- runtime: `java`
- size: `s-1vcpu-2gb`
- build: `./mvnw -q -DskipTests package`
- start: `java -jar $(ls target/*.jar | grep -v -- '-plain' | head -n 1)`

## Steps

1. **Build and start.** `./mvnw -q -DskipTests package` producing one uber-jar (`quarkus.package.jar.type=uber-jar`), then `java -jar` on the jvm-21 template (Temurin JDK 21) with `quarkus.http.port` read from `PORT`; 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
   ```

## Tested examples

- **Quarkus pattern fixture** (tests/deploy-canaries/quarkus-patterns): Verified schema changes on Quarkus.

## Success checks

- app responds on its public URL (`/` on the live URL, expect ample canary quarkus patterns)
- migrated check from the example (`/p/migrated` on the live URL, expect see the pattern fixture checks)

## Limitations

- Verified on the jvm-21 template at `s-1vcpu-2gb`; other sizes and Quarkus major versions are not verified.
- Region, compliance attestations and request-duration limits are unknown and not claimed.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.

## Cost estimate

Estimated **10.00 USD** per month (size prices from `pricing.toml` at build revision `a1b8c38919e59cd035ebabaced73cf84ece24371`).
- app server x1 `s-1vcpu-1gb`: **5.00 USD**
- managed PostgreSQL database 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.

## Verification evidence

- canary_run on 2026-09-21T00:35:31Z at revision `c6c81daa9272c95c5ce381005ba7347a341e578f-dirty (CLI 0.1.21)`: Quarkus pattern fixture deployed on Ample (`./mvnw -q -DskipTests package` producing one uber-jar (`quarkus.package.jar.type=uber-jar`), then `java -jar` on the jvm-21 template (Temurin JDK 21) with `quarkus.http.port` read from `PORT`); for this guide: a --release-command migration ran before activation and its marker was readable by the live app (migrated=release-ok). (expires 2027-03-20T00:35:31Z)

## 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 `current`, required scopes: `servers:write`, `databases:read`.