Apply database schema changes for Quarkus · Ample Computer

Apply database schema changes for Quarkus

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.

What it runs on

You need

Exact tested configuration

  1. ./mvnw -q -DskipTests package

  2. Runtime: java

  3. Sizes: 1vcpu-2gb

  4. Start: java -jar $(ls target/*.jar | grep -v -- '-plain' | head -n 1)

  5. Template: jvm-21

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
    

How it was checked

Evidence

  1. November 6, 2026 · canary run

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

Tested examples

What it doesn’t cover