Deliver public assets through CDN for Rails · Ample Computer

Deliver public assets through CDN for Rails

Cdn assets for a Rails app on Ample. Verified on Rails: 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 rails server reading PORT on the ruby-3.4 template with RAILS_ENV=production.

What it runs on

You need

Exact tested configuration

installbundle config set --local path vendor/bundle && bundle config set --local without 'development test' && bundle install
runtimeruby
sizes-1vcpu-1gb
startbundle exec rails server -b 0.0.0.0 -p $PORT
templateruby-3.4

Steps

  1. Build and start. bundle install into vendor/bundle from Gemfile.lock (development and test groups skipped), then Puma via rails server reading PORT on the ruby-3.4 template with RAILS_ENV=production; 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 rails 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
    Rails pattern fixture deployed on Ample (bundle install into vendor/bundle from Gemfile.lock (development and test groups skipped), then Puma via rails server reading PORT on the ruby-3.4 template with RAILS_ENV=production); 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