Heroku

Search…
Heroku
Manual deployment
This tutorial assumes that you have already managed to clone CONSUL on your machine and gotten it to work.
1.First, create a Heroku account if it isn't already done.
2.Install the Heroku CLI and sign in using
1
heroku login
Copied!
1.Go to your CONSUL repository and instantiate the process
1
cd consul
2
heroku create your-app-name
Copied!
You can add the flag --region eu if you want to use their European servers instead of the US ones.
If your-app-name is not already taken, Heroku should now create your app.
1.Create a database using
1
heroku addons:create heroku-postgresql
Copied!
You should now have access to an empty Postgres database whose address was automatically saved as an environment variable named DATABASE_URL. CONSUL will automatically connect to it when deployed.
1.(Not needed) Add a file name heroku.yml at the root of your project and paste the following in it
1
build:
2
  languages:
3
    - ruby
4
  packages:
5
    - imagemagick
6
run:
7
  web: bundle exec rails server -e ${RAILS_ENV:-production}
Copied!
1.Now, generate a secret key and save it to an ENV variable named SECRET_KEY_BASE using
1
heroku config:set SECRET_KEY_BASE=$(rails secret)
Copied!
Also add your server address:
1
heroku config:set SERVER_NAME=myserver.address.com
Copied!
You need to let the app know where the configuration variables are stored by adding a link to the ENV variables in config/secrets.yml
1
production:
2
  secret_key_base: <%= ENV["SECRET_KEY_BASE"] %>
3
  server_name: <%= ENV["SERVER_NAME"] %>
Copied!
and commit this file in the repo by commenting out the corresponding line in the .gitignore.
1
#/config/secrets.yml
Copied!
Remember not to commit the file if you have any sensitive information in it!
1.You can now push your app using
1
git push heroku your-branch:master
Copied!
1.It won't work straight away because the database doesn't contain the tables needed. To create them, run
1
heroku run rake db:migrate
2
heroku run rake db:seed
Copied!
If you want to add the test data in the database, move gem 'faker', '~> 1.8.7' outside of group :development and run
1
heroku config:set DATABASE_CLEANER_ALLOW_REMOTE_DATABASE_URL=true
2
heroku config:set DATABASE_CLEANER_ALLOW_PRODUCTION=true
3
heroku run rake db:dev_seed
Copied!
1.Your app should now be ready to use. You can open it with
1
heroku open
Copied!
You also can run the console on heroku using
1
heroku console --app your-app-name
Copied!
1.Heroku doesn't allow to save images or documents in its servers, so it's necessary to setup a permanent storage space.
See our S3 guide for more details about configuring Paperclip with S3.
Configure Sendgrid
Add the SendGrid add-on in Heroku. It will create a SendGrid account for you with ENV["SENDGRID_USERNAME"] and ENV["SENDGRID_PASSWORD"].
Add this to config/secrets.yml, under the production: section:
1
  mailer_delivery_method: :smtp
2
  smtp_settings:
3
    :address: "smtp.sendgrid.net"
4
    :port: 587
5
    :domain: "heroku.com"
6
    :user_name: ENV["SENDGRID_USERNAME"]
7
    :password: ENV["SENDGRID_PASSWORD"]
8
    :authentication: "plain"
9
    :enable_starttls_auto: true
Copied!
Important: Turn on one worker dyno so that emails get sent.
Optional but recommended:
Install rails_12factor and specify the Ruby version
The rails_12factor is only useful if you use a version of CONSUL older than 1.0.0. The latter uses Rails 5 which includes the changes.
As recommended by Heroku, you can add the gem rails_12factor and specify the version of Ruby you want to use. You can do so by adding
1
gem 'rails_12factor'
2
​
3
ruby 'x.y.z'
Copied!
in the file Gemfile_custom, where x.y.z is the version defined in the .ruby-version file in the CONSUL repository. Don't forget to run
1
bundle install
Copied!
to generate Gemfile.lock before commiting and pushing to the server.
Use Puma as a web server
Heroku recommends to use Puma to improve the responsiveness of your app on a number of levels.
If you want to allow more concurrency, uncomment the line:
1
workers ENV.fetch("WEB_CONCURRENCY") { 2 }
Copied!
You can find an explanation for each of these settings in the Heroku tutorial.
The last part is to change the web task to use Puma by changing it to this in your heroku.yml file:
1
web: bundle exec puma -C config/puma.rb
Copied!
Add configuration variables to tune your app from the dashboard
The free and hobby versions of Heroku are barely enough to run an app like CONSUL. To optimise the response time and make sure the app doesn't run out of memory, you can change the number of workers and threads that Puma uses.
My recommended settings are one worker and three threads. You can set it by running these two commands:
1
heroku config:set WEB_CONCURRENCY=1
2
heroku config:set RAILS_MAX_THREADS=3
Copied!
I also recommend to set the following:
1
heroku config:set RAILS_SERVE_STATIC_FILES=enabled
2
heroku config:set RAILS_ENV=production
Copied!
Digital Ocean
Docker
Last modified 1mo ago
Copy link
Contents
Manual deployment
Configure Sendgrid
Optional but recommended:
Install rails_12factor and specify the Ruby version
Use Puma as a web server
Add configuration variables to tune your app from the dashboard