# 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

- [Computeverified](/content/discover/primitive/compute/index.html)
  Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [CDNverified](/content/discover/primitive/cdn/index.html)
  A published bucket's objects are served from its public URL; set Cache-Control when uploading to control caching. App responses are served by the app.

## You need

- A Sinatra project (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)

- A bucket from `ample bucket create` with credentials passed as encrypted S3_* environment variables

- An Ample account token with servers:write, buckets:read

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

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

```bash
$ 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

-  **Sinatra pattern fixture.** Verified CDN assets on Sinatra.

## What it doesn’t cover

- Verified on the ruby-3.4 template at s-1vcpu-1gb.
- The CDN serves published-bucket objects; control caching with Cache-Control on upload and versioned keys.
