Deliver public assets through CDN for Gin · Ample Computer

Deliver public assets through CDN for Gin

Cdn assets for a Gin app on Ample. Verified on Gin: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL. Build and start: CGO_ENABLED=0 go build -o app ./... then ./app on the ubuntu-24.04 template (go.sum committed for a reproducible build).

What it runs on

You need

Exact tested configuration

build CGO_ENABLED=0 go build -o app ./...

runtime go

sizes - 1vcpu-1gb

start ./app

template ubuntu-24.04

Steps

  1. Build and start. CGO_ENABLED=0 go build -o app ./... then ./app on the ubuntu-24.04 template (go.sum committed for a reproducible build); 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 gin patterns”
✓ versioned-static-assets check from the example · http get/p/versioned-static-assets → “see the pattern fixture checks”

Evidence

  1. November 5, 2026 · canary run

    Gin pattern fixture deployed on Ample (CGO_ENABLED=0 go build -o app ./... then ./app on the ubuntu-24.04 template (go.sum committed for a reproducible build)); 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