# Deliver public assets through CDN for Quarkus

Cdn assets for a Quarkus app on Ample. Verified on Quarkus: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL. 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

- [Compute verified](/content/discover/primitive/compute/index.html)  
  Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [CDN verified](/content/discover/primitive/cdn/index.html)  
  A published bucket's objects are served from its public URL; set Cache-Control when uploading to control caching. App responses are served by the app.

## You need
- A Quarkus project (`./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 bucket from `ample bucket create` with credentials passed as encrypted S3_* environment variables
- An Ample account token with `servers:write`, `buckets:read`

## Exact tested configuration
- **build**: `./mvnw -q -DskipTests package`
- **runtime**: java
- **sizes**: 1vcpu-2gb
- **start**: `java -jar $(ls target/*.jar | grep -v -- '-plain' | head -n 1)`
- **template**: jvm-21

## 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. **Publish a bucket for public assets.** Publish only the asset bucket; upload versioned keys with an immutable Cache-Control header and build URLs from its public URL.
   
   ```sh
   $ ample bucket publish <bucket-name>
   ```

3. **Verify.** Fetch the live URL and `/p/versioned-static-assets` on the example; on failure read the build and runtime logs.
   
   ```sh
   $ ample logs <deployment_id> --kind build
   ```

## How it was checked

✓ app responds on its public URL: `http get/` → “ample canary quarkus patterns”  
✓ versioned-static-assets check from the example: `http get/p/versioned-static-assets` → “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: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL.

## Tested examples

- **Quarkus pattern fixture.** Verified CDN assets on Quarkus.

## What it doesn’t cover
- Verified on the jvm-21 template at s-1vcpu-2gb.
- The CDN serves published-bucket objects; control caching with Cache-Control on upload and versioned keys.
