Configure build and start for Quarkus · Ample Computer

Configure build and start for Quarkus

Build and start for a Quarkus app on Ample. Verified on Quarkus: the app built and started with the documented commands and answered on its public HTTPS URL. 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.

Verified November 6, 2026

What it runs on

You need

Exact tested configuration

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. Deploy. Run the synchronous deploy once and read the result.

   $ ample deploy . --name <app-name> --public
  1. Verify. Fetch the live URL 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 quarkus patterns”

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: the app built and started with the documented commands and answered on its public HTTPS URL.

Tested examples

What it doesn’t cover