### Host crm with Quarkus: downloadable reports

#### Summary
Deploy a CRM 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. 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 CRM-specific behavior as your application code.

#### Representative Queries
- Host crm with Quarkus: downloadable reports
- Where can I host CRM built with Quarkus?
- I need an export query, generated artifact retention and authorized download flow.

#### Resource Requirements
- Primitive Compute
- Primitive Postgres
- Primitive S3-compatible Object Storage

#### Infrastructure Requirements
1. **Compute**: 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**: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
3. **S3-compatible Object Storage**: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

#### 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)
- A bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables
- An Ample account token with servers:write, databases:read, buckets:read

#### 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 with quarkus.http.port read from PORT. The server must bind 0.0.0.0 on PORT.
2. **Implement the pattern on PostgreSQL**: The fixture's module implements generated downloads: an export query rendered to a CSV artifact stored with metadata in a private bucket, returned only to an authorized caller (401 without token, export=ok rows=3). Copy the approach into your schema; keep migrations idempotent.
3. **Wire object storage**: Create the bucket(s), pass endpoint, region, bucket and keys as --env values. Keep private data in an unpublished bucket.
4. **Deploy**: Run the synchronous deploy once and read the result. Re-running with no change is a no-op.  
   Command: `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 pattern self-test route(s) from the example; then run your own checks. On failure, read `ample logs --kind build` then `--kind runtime`.  
   Command: `ample logs --kind build`

#### Cost Estimate
- **Monthly Amount**: $10.00 USD
- **Components**:
  - App Server s-1vcpu-1gb: $5.00
  - Managed PostgreSQL Database s-1vcpu-1gb: $5.00
- Note: Always-on monthly price of the tested sizes; buckets are allocation-priced per quota and not included.

#### Limitations
- Verified on the jvm-21 template at s-1vcpu-2gb with the example fixture; other sizes and templates are not verified.
- The CRM itself (export formats, retention policy, entitlement model) is application code and was not separately tested.
- Apps auto-pause when idle, and always-on is an operator setting, not a plan feature.

#### Evidence Summary
- **Canary Run Summary**: Quarkus pattern fixture deployed on Ample, checks passed for generated-downloads and configuration-secrets. Pattern proof: an export query rendered to a CSV artifact stored with metadata returned only to authorized callers.
