# The Power of Using Production In Development

DevFeed: [The Power of Using Production In Development](<https://devfeed.tech/articles/the-power-of-using-production-in-development-28261.md>)

Original publisher: [Read original article](<http://fuzzyblog.io/blog/rails/2020/02/01/the-power-of-production-in-development.html>)

Author: Fuzzygroup

Published: 2020-02-01T00:00:00Z

Content type: tutorial

Language: en

Sources: [Scott Johnson](<https://devfeed.tech/sources/scott-johnson.md>)

Topics: [Rails](<https://devfeed.tech/topics/rails.md>), [Development](<https://devfeed.tech/topics/development.md>)

Tags: [console](<https://devfeed.tech/tags/console.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [development](<https://devfeed.tech/tags/development.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [production](<https://devfeed.tech/tags/production.md>), [rails](<https://devfeed.tech/tags/rails.md>)

## AI overview

This Rails troubleshooting tip recommends running the application locally in production mode and checking whether the Rails console starts. The author suggests that a working production console can reveal deployment-related issues.

## Source excerpt

I spent a lot of time today trying to get something to deploy and hitting a near unending set of small issues that still broke the entire deploy (Rails in production mode is WAY less forgiving than Rails in development mode). And, to be honest, the constant stream of cursing was, perhaps, my less than finest moment (friends of mine, at least two, are now laughing hard). An old school trick for helping with this is to run production mode locally and see if rails console comes up. As a general rule of thumb, if rails console works, then rails itself will work. Here's how to do this: RAILS_ENV=production bundle exec rails c And this one, simple, stupid trick tends to reveal a lot of issues. Recommended.