Configure environment and secrets for Sinatra · Ample Computer

Configure environment and secrets for Sinatra

Configuration and secrets for a Sinatra app on Ample. Verified on Sinatra: an --env value delivered encrypted and reported as present without being echoed (secret=set). 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.

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 rackup -o 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 rackup (config.ru) reading PORT on the ruby-3.4 template; the server must bind 0.0.0.0 on PORT.

  2. Pass values on deploy. Use --env KEY=value (repeatable) or --env-file; values are encrypted at rest and reused on redeploys. Declare names only in ample.toml.

   $ ample deploy . --name <app-name> --public --env MY_SECRET=...
  1. Verify. Fetch the live URL and /p/configuration-secrets 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”
✓configuration-secrets check from the example· http get/p/configuration-secrets → “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: an --env value delivered encrypted and reported as present without being echoed (secret=set).

Tested examples

What it doesn’t cover