Deliver public assets through CDN for Axum · Ample Computer

Deliver public assets through CDN for Axum

Cdn assets for a Axum app on Ample. Verified on Axum: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL. Build and start: cargo build --release in the rust builder image (stable toolchain, Cargo.lock committed, pure-Rust dependencies), then the release binary on the ubuntu-24.04 template reading PORT and DATABASE_URL.

Verified November 5, 2026

What it runs on

You need

Exact tested configuration

Steps

  1. Build and start. cargo build --release in the rust builder image (stable toolchain, Cargo.lock committed, pure-Rust dependencies), then the release binary on the ubuntu-24.04 template reading PORT and DATABASE_URL; 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.

    $ 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.

    $ ample logs <deployment_id> --kind build
    

How it was checked

✓ app responds on its public URL
✓ versioned-static-assets check from the example

Evidence

  1. November 5, 2026 · canary run
    Axum pattern fixture deployed on Ample (cargo build --release in the rust builder image (stable toolchain, Cargo.lock committed, pure-Rust dependencies), then the release binary on the ubuntu-24.04 template reading PORT and DATABASE_URL); for this guide: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL.

Tested examples

What it doesn’t cover