- Action Cable
- Action Mailbox
- Action Text
- Active Storage
- Background Workers
- Billing & Payments
- Cron & Scheduled Jobs
Deploying Jumpstart Pro is easy. We've even configured a staging environment for you.
You'll need a Redis and PostgreSQL database setup to deploy Jumpstart Pro.
Jumpstart Pro is preconfigured with two environments for deploying: staging and production.
Background workers will be configured to run in all environments so you will have the same experience in development as you will in staging and production.
Email providers will only be configured for production by Jumpstart Pro, so you don't accidentally send emails to real users in staging.
You will need to take the contents of
config/credentials/production.key (depending on what env you're deploying) and set the
RAILS_MASTER_KEY environment variable to the contents of this file. This will allow staging or production to decrypt your credentials for the correct environment.
Hatchbox.io is built by the makers of Jumpstart Pro and GoRails. It's a fantastically simple and cheap option for deploying apps to your own servers.
Deploying to Heroku is easy. Jumpstart Pro includes a Procfile to help automatically configure your Heroku processes.
First, you'll need to install the Heroku CLI and login with
Now you can create a Heroku app by running
heroku create myapp
heroku addons:create heroku-postgresql:hobby-dev heroku addons:create heroku-redis:hobby-dev
Afterwards, you need to add the
RAILS_MASTER_KEY environment variable and set it equal to the key inside
Then you can deploy your code to Heroku and run migrations.
git push heroku master heroku run rails db:migrate
We provide a sample Dockerfile and docker-compose.yml for you in case you'd like to deploy your application using Docker.