Deliver public assets through CDN for Sinatra | Ample

INFRASTRUCTURE

What it needs

PREREQUISITES

Before you start

TESTED CONFIGURATION

Exactly what was tested

STEP BY STEP

How to do it

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

EXAMPLES

Tested examples

SUCCESS CHECKS

How to know it worked

LIMITATIONS

Know the limits

COST

Cost estimate

Estimated 5.00 USD per month (size prices from pricing.toml at build revision a1b8c38919e59cd035ebabaced73cf84ece24371).

Always-on monthly price of the tested sizes; apps auto-pause when idle. Buckets are allocation-priced per quota and not included.

EVIDENCE

Verification evidence

EXECUTION

Execution binding

MCP tool ample_deploy (registry mcp:ample_deploy), schema hash 876465fce906da0c observed 2026-09-21T03:19:59.461917+00:00 at revision 49962bcade4f. Binding state at export: current. Required scopes: servers:write, buckets:read.

NEXT ACTIONS

Typed next actions