How to Run a Rails App in Production Locally

running_app_in_production_locally.markdown

1. Add gem 'rails_12factor' to your Gemfile. This will add error logging and the ability for your app to serve static assets.
2. bundle
3. Run RAILS_ENV=production rake db:create db:migrate db:seed
4. Run rake secret and copy the output
5. From the command line: export SECRET_KEY_BASE=output-of-rake-secret
6. To precompile your assets, run rake assets:precompile. This will create a folder public/assets that contains all of your assets.
7. Run RAILS_ENV=production rails s and you should see your app.

Remember to clobber your assets (rake assets:clobber) and re-precompile (rake assets:precompile) if you make changes.

1. Run **_

RAILS_ENV=production rake db:create db:migrate db:seed

**
2. Run **

rake secret

** and copy the output
3. From the command line : **

export SECRET_KEY_BASE=output-of-rake-secret

**
4. Change production.rb file config.assets.compile = false to **

config.assets.compile = true

**
5.To precompile your assets, run **

RAILS_ENV=production bundle exec rake assets:precompile

**. This will create a folder public/assets that contains all of your assets.
6.Run **

RAILS_ENV=production rails s

_** and you should see your app.

Thank you so much. The steps are very clear.
Do I need to upload the compiled assets files(in public folder) to GITHUB if I want to deploy in Heroku?

@gowritumma Nope. Heroku should compile the assets automatically.

thank you ❤️

Thank you so much. I am following all steps resolved the bugs.

Thank you very much

RAILS_SERVE_STATIC_FILES=true

Lifesaver with React Rails https://github.com/reactjs/react-rails

I use this command for puma on prod env

rails s -e production

Also needed to set
config.force_ssl = false