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.
On Oct 5, 2012, at 11:50 AM, Jeremy Kemper <[email protected]> wrote: > On Fri, Oct 5, 2012 at 9:54 AM, Robert Evans <[email protected]> wrote: > It's a pretty common practice (and best practice) to not include your > config/database.yml file inside your git repo. I'd like to add > config/database.yml to the generated .gitignore file when creating a new > rails application. Any objects, concerns, etc. before I got submit a PR? > > -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. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/rubyonrails-core?hl=en. ========= Robert Evans Code Wranglers, Inc http://www.codewranglers.org http://www.github.com/revans http://www.linkedin/in/rrevans -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
