ShippedRails hosting
on Shipped.
Give your Rails application a home for its pages, records, uploads, and jobs. Keep building features while Shipped handles the infrastructure.
Run the Rails application in production
Deploy your Rails app with its Ruby runtime, gems, production server, and compiled assets. Supply private configuration through secrets and connect the application to its database. Shipped manages the public address and HTTPS so your routes, controllers, and views can serve customers under your own domain.
Let jobs and uploads grow with the app
Run your selected job backend in a separate worker when work should happen outside the web request. Connect persistent object storage for uploaded attachments using an appropriate storage integration. Transactional email gives account messages and notifications a delivery service without making the web process manage mail infrastructure.
Treat migrations as part of the release
Check new models and schema changes against staging data before deploying them to production. Keep database changes compatible with the releases you may need to restore. Deployment rollback returns to earlier application code; it does not remove newly created records or automatically undo a migration.
A little more detail
Questions about Rails?
Can Rails jobs use a separate worker?
Yes. Deploy the worker for the job backend your app uses and connect it to the necessary database or queue. Its process and capacity can be managed separately from the web service.
Where should Rails attachments live?
Use persistent storage through your chosen attachment integration. Files created by users should survive application image replacement and should be included in your data recovery plan.
From your workspace to the web