Delivery for Ruby on Railss
Delivery in Rails is moving an app from a laptop to a running server. It covers production configuration, environment variables and credentials, database setup, asset precompilation and a deploy tool such as Kamal, Docker or a platform service. Health checks, logs and error tracking show whether the release is healthy.
Stage: Quality and Deployment · Part of the Ruby on Rails roadmap · Last reviewed 19 November 2026
What to learn in Delivery
- Set production configuration and secrets with encrypted credentials
- Build a Docker image of a Rails app
- Run database migrations safely during a deploy
- Deploy with Kamal or a hosting platform
- Add logging and error tracking to a live app
Delivery interview questions
How does Rails store secrets in production?
Encrypted credentials keep secrets in config/credentials.yml.enc, decrypted with a master key kept out of version control and provided through RAILS_MASTER_KEY or a key file. Environment variables are another common option for deployed services.
Why run migrations carefully during deploys?
Old code may still run while the schema changes. A migration that drops or renames a column can break running requests. Safer practice is to add columns first, deploy code that uses them, and remove unused columns in a later release.
Where Delivery fits in the Ruby on Rails roadmap
Delivery belongs to the Quality and Deployment stage (advanced level). Ship.
Other units in this stage
Back to the full Ruby on Rails roadmap