Storing your production credentials in your repository is a bad idea. A very bad idea. Even if it's encrypted.
Putting aside the obvious security issues with this, the scope for accidentally using production credentials in a development environment scares me to death. I never want my local development copy of an application to know anything about production. I rest easy knowing if I was to run rake db:reset
in development, there's no chance of anything bad happening to our production environment.
There's nothing wrong with encrypting your config files but storing them in your repository... ??. I'm sad that Rails encourages this behaviour.
Some other recent posts
My development environment
In this video I'm taking a quick look at my development environment. Looking at code editor, terminal, databases, containers, web servers and more.
A quick intro to service classes
To get things started, in this video I'm looking at how service classes are used in the application. Service classes form the basis for much of the logic within this app so it's a good place to start
I'm building an app hosting platform
I'm building a app hosting platform and in this video I'm going to introduce you to the project and show you what I've got so far.