# Host recruiting tracker with Quarkus: relational workspace data

Deploy a recruiting 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 recruiting tracker-specific behavior as your application code.

## Representative Queries
- Host recruiting tracker with Quarkus: relational workspace data
- Where can I host Recruiting tracker built with Quarkus?
- I need a workspace-specific schema, state transitions and access rules.

## Resource Requirements
- primitive:compute
- primitive: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.

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

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

## Success Checks
- App responds on its public URL (kind: http_get, path: /, expect: ample canary quarkus patterns)
- 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 recruiting tracker itself (your record schema, states and access rules) is application code and was not separately tested; the pattern checks are what was verified.

## Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Note**: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.
- Components:
  - App server: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0
  - Managed PostgreSQL database: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0

## Example
- **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 Ref: tests/deploy-canaries/quarkus-patterns

## Next Actions
1. **Browse the catalog index**  
2. **Search published recipes by intent, stack and constraints**  
3. **Prepare a side-effect-free deployment plan for an authorized project**  
4. **Read the existing agent authentication setup**  
5. **Browse Recruiting tracker**  
6. **Browse Quarkus**  
7. **Browse Relational records**  
8. **Browse Deploy web app**