Apply database schema changes for Spring Boot · Ample Computer
Apply database schema changes for Spring Boot
Schema changes for a Spring Boot app on Ample. Verified on Spring Boot: 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 (or the Gradle wrapper) producing one application jar, then java -jar on the jvm-21 template (Temurin JDK 21) with server.port read from PORT.
What it runs on
Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.Postgresverified
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 Spring Boot project (./mvnw -q -DskipTests package (or the Gradle wrapper) producing one application jar, then java -jar on the jvm-21 template (Temurin JDK 21) with server.port read from PORT)
- A PostgreSQL driver reading DATABASE_URL at runtime
- An Ample account token with servers:write, databases:read
Exact tested configuration
build./mvnw -q -DskipTests package
runtimejava
sizes-1vcpu-2gb
startjava -jar $(ls target/*.jar | grep -v -- '-plain' | head -n 1)
templatejvm-21
Steps
Build and start. ./mvnw -q -DskipTests package (or the Gradle wrapper) producing one application jar, then java -jar on the jvm-21 template (Temurin JDK 21) with server.port read from PORT; 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 <app-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 <deployment_id> --kind build
How it was checked
✓app responds on its public URL· http get/ → “ample canary spring boot patterns”
✓migrated check from the example· http get/p/migrated → “see the pattern fixture checks”
Evidence
- November 6, 2026 · canary run
Spring Boot pattern fixture deployed on Ample (./mvnw -q -DskipTests package (or the Gradle wrapper) producing one application jar, then java -jar on the jvm-21 template (Temurin JDK 21) with server.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).
Tested examples
- Spring Boot pattern fixture. Verified schema changes on Spring Boot.
What it doesn’t cover
- Verified on the jvm-21 template at s-1vcpu-2gb.
- Managed PostgreSQL 16 with pgvector.