Diagnose deployment failures for Rails · Ample Computer
Diagnose deployment failures for Rails
Deployment diagnostics for a Rails app on Ample. Verified on Rails: the same app deployed with a deliberate boot failure (CANARY_FAIL=boot): ample deploy exited 1 with a coded failure (health_check_failed when the process dies at boot, public_ingress_failed when the framework boots but every request answers 500) and the app's own error line was readable with ample logs <deployment_id> --kind runtime, so the cause is read from the framework's output rather than guessed. 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.
Verified November 6, 2026
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
Read the failure code. Deploy is synchronous. Exit 1 with build_failed means the isolated build failed; health_check_failed means the app built but never answered on PORT (it crashed at boot or bound the wrong port); public_ingress_failed means it answered on PORT but the public URL returned an error status (a request handler or bootstrap failed); exit 2 means a required preflight action is blocking.
Read the build log. The last lines name the failing command and its output.
$ ample logs <deployment_id> --kind build
- Read the runtime log. For health_check_failed the runtime log carries the Rails process output: in the verified run the deliberate boot failure's own error line was there, followed by the platform's health-check verdict and the start command it ran.
$ ample logs <deployment_id> --kind runtime
Fix and redeploy once. Change the source, the environment or the command override, then run ample deploy again. Do not loop deploys to poll status; an unchanged redeploy is a no-op.
Verify. Fetch the live URL on the example; on failure read the build and runtime logs.
$ ample logs <deployment_id> --kind build
How it was checked
✓ failed deploy reports health_check_failed synchronously · manual → “ample deploy exits 1 with error.code health_check_failed”
✓ runtime log carries the app's own error line · manual → “ample logs
Evidence
- November 6, 2026 · canary run
Rails pattern fixture deployed on Ample with CANARY_FAIL=boot (bundle install into vendor/bundle from Gemfile.lock (development and test groups skipped), then Puma viarails serverreading PORT on the ruby-3.4 template with RAILS_ENV=production); the same app deployed with a deliberate boot failure (CANARY_FAIL=boot):ample deployexited 1 with a coded failure (health_check_failed when the process dies at boot, public_ingress_failed when the framework boots but every request answers 500) and the app's own error line was readable withample logs <deployment_id> --kind runtime, so the cause is read from the framework's output rather than guessed.
Tested examples
- Rails pattern fixture. Verified deployment diagnostics on Rails.
What it doesn’t cover
- Verified on the ruby-3.4 template at s-1vcpu-1gb.