Deliver public assets through CDN for Astro · Ample Computer

Deliver public assets through CDN for Astro

Cdn assets for a Astro app on Ample. Verified on Astro: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL. Build and start: astro build with the @astrojs/node standalone adapter then node ./dist/server/entry.mjs on the node-22 template.

Verified November 6, 2026

What it runs on

You need

Exact tested configuration

build
npm run build --if-present

install
npm install

runtime
node

sizes-1vcpu-1gb

start
npm run start

template
node-22

Steps

  1. Build and start. astro build with the @astrojs/node standalone adapter then node ./dist/server/entry.mjs on the node-22 template; 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 · http get/ → “ample canary astro 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
    Astro pattern fixture deployed on Ample (astro build with the @astrojs/node standalone adapter then node ./dist/server/entry.mjs on the node-22 template); 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