# Configure build and start for Quarkus

## Summary

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.

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

## 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)
- An Ample account token with `servers:write`

## 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. **Deploy.** Run the synchronous deploy once and read the result.
   ```
   ample deploy . --name <app-name> --public
   ```
3. **Verify.** Fetch the live URL 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 build and start on Quarkus.

## Success checks

- app responds on its public URL (`/` on the live URL, expect ample canary quarkus patterns)

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

## Cost estimate

Estimated **5.00 USD** per month (size prices from `pricing.toml` at build revision `a1b8c38919e59cd035ebabaced73cf84ece24371`).
- app server 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: the app built and started with the documented commands and answered on its public HTTPS URL. (expires `2027-03-20T00:35:31Z`)

Last verified: `2026-09-21T00: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`.