Configure environment and secrets for Quarkus · Ample Computer

Configure environment and secrets for Quarkus

Configuration and secrets for a Quarkus app on Ample. Verified on Quarkus: an --env value delivered encrypted and reported as present without being echoed (secret=set). 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. Pass values on deploy. Use --env KEY=value (repeatable) or --env-file; values are encrypted at rest and reused on redeploys. Declare names only in ample.toml.

    $ ample deploy . --name <app-name> --public --env MY_SECRET=...
    
  3. Verify. Fetch the live URL and /p/configuration-secrets 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”
✓ configuration-secrets check from the example · http get/p/configuration-secrets → “see the pattern fixture checks”

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: an --env value delivered encrypted and reported as present without being echoed (secret=set).

Tested examples

What it doesn’t cover