-1. It’s well-meaning but painful for typical app development and for folks new to Rails.
A comment in config/database.yml about production best practices would work, or a link to a broader discussion of production deployment.
OK - I actually wasn’t thinking about those who use DB’s without a username/password and keep the database.yml in the git repo. I still think we could do something better here (e.g. stubbed database.yml file as Prem suggested), but I certainly can understand the points made in this thread.