page:recipes:inventory manager:quarkus:report exports

Host Inventory Manager with Quarkus: Downloadable Reports

Deploy an inventory manager built with Quarkus on Ample using the generated downloads pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, a managed PostgreSQL 16 database is auto-provisioned and injected as DATABASE_URL, a private S3-compatible bucket holds objects with credentials delivered as encrypted environment variables.

Summary

Verified on Quarkus: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). Not separately tested: your export formats, retention policy, and entitlement model; treat the inventory manager-specific behavior as your application code.

Representative Queries

Resource Requirements

Infrastructure Requirements

Compute

Postgres

S3-compatible Object Storage

Prerequisites

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

  2. Implement the Pattern on PostgreSQL
    The fixture's module implements generated downloads.

  3. Wire Object Storage
    Create the bucket(s) then pass endpoint, region, bucket, and keys as --env values.

  4. Deploy
    Run the synchronous deploy once and read the result. ample deploy . --name --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...

  5. Verify
    Fetch the live URL and the pattern self-test route(s) from the example; then run your own checks. ample logs --kind build

Example

Quarkus Pattern Fixture

Success Checks

Limitations

Cost Estimate

Evidence Summary

  1. Canary Run: Quarkus pattern fixture deployed on Ample; checks passed for generated-downloads and configuration-secrets.
    • Observed At: 2026-09-21T00:35:31Z
    • Expires At: 2027-03-20T00:35:31Z
  2. Canary Run: The same Quarkus app deployed with a --release-command migration; the marker it created was readable after activation.