Deliver public assets through CDN for Sinatra · Ample Computer

Deliver public assets through CDN for Sinatra

Cdn assets for a Sinatra app on Ample. Verified on Sinatra: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL. Build and start: bundle install into vendor/bundle from Gemfile.lock (development and test groups skipped), then Puma via rackup (config.ru) reading PORT on the ruby-3.4 template.

Verified November 5, 2026

What it runs on

You need

Exact tested configuration

install bundle config set --local path vendor/bundle && bundle config set --local without 'development test' && bundle install

run time ruby

sizes-1vcpu-1gb

start bundle exec rackup -o 0.0.0.0 -p $PORT

template ruby-3.4

Steps

  1. Build and start. bundle install into vendor/bundle from Gemfile.lock (development and test groups skipped), then Puma via rackup (config.ru) reading PORT on the ruby-3.4 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>
  1. 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 sinatra 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

Sinatra pattern fixture deployed on Ample (bundle install into vendor/bundle from Gemfile.lock (development and test groups skipped), then Puma via rackup (config.ru) reading PORT on the ruby-3.4 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