The generator has created the necessary files and gems for deployment to Heroku. If you have installed manually, you will need to provide these files yourself:
Procfile
: used by Heroku and Foreman to start the Puma server.buildpacks
: used to install Ruby and Node environments12factor
gem: required by Heroku'puma'
gem: recommended Heroku webserverconfig/puma.rb
: Puma webserver config filelib/tasks/assets.rake
: This rake task file is provided by the generator regardless of whether the user chose Heroku Deployment as an option. It is highlighted here because it is helpful to understand that this task is what generates your JavaScript bundles in production.
React on Rails requires both a ruby environment (for Rails) and a Node environment (for Webpack), so you will need to have Heroku use multiple buildpacks. Currently, we would suggest using DDollar's Heroku Buildpack Multi.
Assuming you have downloaded and installed the Heroku command-line utility and have initialized the app, you will need to tell Heroku to use Heroku Buildpack Multi via the command-line:
heroku buildpacks:set https://github.com/heroku/heroku-buildpack-multi
Heroku will now be able to use the multiple buildpacks specified in .buildpacks
.
Note, an alternative approach is to use the Heroku Toolbelt to set buildpacks.
- Delete the line with
sqlite
and replace it with:
gem 'pg'
- Replace your
database.yml
file with this (assuming your app name is "ror")
default: &default
adapter: postgresql
username:
password:
host: localhost
development:
<<: *default
database: ror_development
# Warning: The database defined as "test" will be erased and
# re-generated from your development database when you run "rake".
# Do not set this db to the same as development or production.
test:
<<: *default
database: ror_test
production:
<<: *default
database: ror_production
Run:
bundle
bin/rake db:migrate
bin/rake db:setup