# Configure environment and secrets for Sinatra

## Summary

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.

## Infrastructure requirements

- Compute: verified (Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.)

## Prerequisites

- 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)
- An Ample account token with servers:write

## Exact tested configuration

- template: `ruby-3.4`
- runtime: `ruby`
- size: `s-1vcpu-1gb`
- install: `bundle config set --local path vendor/bundle && bundle config set --local without 'development test' && bundle install`
- start: `bundle exec rackup -o 0.0.0.0 -p $PORT`

## 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=...
   ```
3. **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
   ```

## Tested examples

- **Sinatra pattern fixture** (tests/deploy-canaries/sinatra-patterns): Verified configuration and secrets on Sinatra.

## Success checks

- app responds on its public URL (`/` on the live URL, expect ample canary sinatra patterns)
- configuration-secrets check from the example (`/p/configuration-secrets` on the live URL, expect see the pattern fixture checks)

## Limitations

- Verified on the ruby-3.4 template at s-1vcpu-1gb; other sizes and Sinatra major versions are not verified.
- Region, compliance attestations and request-duration limits are unknown and not claimed.

## Cost estimate

Estimated 5.00 USD per month (size prices from pricing.toml at build revision a1b8c38919e59cd035ebabaced73cf84ece24371).
- app server x1 `s-1vcpu-1gb`: 5.00 USD

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

## Verification evidence

- canary_run on 2026-09-20T23:45:31Z at revision `4d1511e574302f3904b75088bd4048a0975218b3-dirty (CLI 0.1.21)`: 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). (expires 2027-03-19T23:45:31Z)

Last verified: 2026-09-20T23:45:31Z

## 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 `current`, required scopes: servers:write.