Host project tracker with Quarkus: relational workspace data

Summary

Deploy a project tracker built with Quarkus on Ample using the relational records 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. Verified on Quarkus: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). Not separately tested: your record schema, states and access rules; treat the project tracker-specific behavior as your application code.

Prerequisites

• A Quarkus project that builds and starts with the documented commands (./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)
• A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
• An Ample account token with servers:write, databases:read

Resource Requirements

• Compute
• Postgres

Infrastructure Requirements

1. Compute
   • Status: verified
   • Summary: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
2. Postgres
   • Status: verified
   • Summary: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

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)

Workflow Steps

1. Build and start
   Command: ./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. Implement the pattern on PostgreSQL
   Body: The fixture's module implements relational records: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.

3. Deploy
   Command: ample deploy . --name --public Body: Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked). Re-running with no change is a no-op.

4. Verify
   Command: ample logs --kind build
   Body: Fetch the live URL and the pattern self-test route(s) (/p/relational-records) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime.

Examples

• Quarkus pattern fixture
  Description: Multi-pattern Quarkus app whose relational records module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
  Source Reference: tests/deploy-canaries/quarkus-patterns

Success Checks

1. App responds on its public URL
   Kind: http_get
   Path: /
   Expect: ample canary quarkus patterns

2. Relational-records self-test
   Kind: http_get
   Path: /p/relational-records
   Expect: records=ok transitions=true isolation=true

Limitations

• Verified on the jvm-21 template at s-1vcpu-2gb with the example fixture; other sizes, templates and Quarkus major versions are not verified.
• The project tracker itself (your record schema, states and access rules) is application code and was not separately tested; the pattern checks are what was verified.
• Region, compliance attestations and request-duration limits are unknown and not claimed.
• Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
• Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Authoritative: true
• Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
• Components:
  • App server:
    • Size: s-1vcpu-1gb
    • Quantity: 1.0
    • Monthly Amount: 5.0
  • Managed PostgreSQL database:
    • Size: s-1vcpu-1gb
    • Quantity: 1.0
    • Monthly Amount: 5.0
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

Evidence Summary

1. Canary Run Summary: 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); checks passed for relational-records and configuration-secrets. Pattern proof: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true).

   • Observed At: 2026-09-21T00:35:31Z
   • Implementation Revision: c6c81daa9272c95c5ce381005ba7347a341e578f-dirty (CLI 0.1.21)
   • Expires At: 2027-03-20T00:35:31Z

2. Canary Run Summary: The same Quarkus app deployed with a --release-command migration; the marker it created was readable after activation.

   • Observed At: 2026-09-21T00:35:31Z
   • Implementation Revision: c6c81daa9272c95c5ce381005ba7347a341e578f-dirty (CLI 0.1.21)
   • Expires At: 2027-03-20T00:35:31Z

Next Actions

1. Browse the catalog index
   Action ID: browse-catalog
   Method: GET
   Relative Path: /v1/catalog

2. Search published recipes by intent, stack and constraints
   Action ID: search-recipes
   Method: POST
   Relative Path: /v1/catalog/search Parameters:

   • Body: {"limit":5,"query":"Host project tracker with Quarkus: relational workspace data"}

3. Prepare a side-effect-free deployment plan for an authorized project
   Action ID: plan:page:recipes:project-tracker:quarkus:relational-workspace
   Method: POST
   Relative Path: /v1/catalog/plan Parameters: {"body":{"inputs":{},"projectId":"","recipeId":"page:recipes:project-tracker:quarkus:relational-workspace","recipeRevision":"r1"}}

4. Read the existing agent authentication setup
   Action ID: auth-setup
   Method: GET
   Relative Path: /mcp/setup

5. Browse Project tracker
   Action ID: browse:workload:project-tracker
   Method: GET
   Relative Path: /v1/catalog/nodes/workload%3Aproject-tracker

6. Browse Quarkus
   Action ID: browse:stack:framework-quarkus
   Method: GET
   Relative Path: /v1/catalog/nodes/stack%3Aframework-quarkus

7. Browse Relational records
   Action ID: browse:pattern:relational-records
   Method: GET
   Relative Path: /v1/catalog/nodes/pattern%3Arelational-records

8. Browse Deploy web app
   Action ID: browse:intent:deploy-web-app
   Method: GET
   Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app