Configure environment and secrets for Rails · Ample Computer
Configure environment and secrets for Rails
Configuration and secrets for a Rails app on Ample. Verified on Rails: 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 rails server reading PORT on the ruby-3.4 template with RAILS_ENV=production.
What it runs on
- Computeverified Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.
You need
- A Rails project (bundle install into vendor/bundle from Gemfile.lock (development and test groups skipped), then Puma via
rails serverreading PORT on the ruby-3.4 template with RAILS_ENV=production) - An Ample account token with servers:write
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
Build and start. bundle install into vendor/bundle from Gemfile.lock (development and test groups skipped), then Puma via
rails serverreading PORT on the ruby-3.4 template with RAILS_ENV=production; the server must bind 0.0.0.0 on PORT.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=...
- 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 rails patterns”
✓ configuration-secrets check from the example · http get/p/configuration-secrets → “see the pattern fixture checks”
Evidence
- 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: an --env value delivered encrypted and reported as present without being echoed (secret=set).
Tested examples
- Rails pattern fixture. Verified configuration and secrets on Rails.
What it doesn’t cover
- Verified on the ruby-3.4 template at s-1vcpu-1gb.