@taboularasa We had a discussion about this in Dev Roundup ~2 years ago between me, you, JD, and Pedro (see 6/27/2014 in the doc). Unfortunately we didn't take notes about the outcome but from what I recall, we decided to not ignore it because the default database.yml in Rails 4 (or 4.1 maybe) reads from the environment by default and PG is configurable in the environment (if you have a password on your local DB for instance). So we opted for the simpler dev machine setup (no need to copy/pasta an example database.yml) since connection credentials can live in the environment instead of that file.
@taboularasa We had a discussion about this in Dev Roundup ~2 years ago between me, you, JD, and Pedro (see 6/27/2014 in the doc). Unfortunately we didn't take notes about the outcome but from what I recall, we decided to not ignore it because the default
database.ymlin Rails 4 (or 4.1 maybe) reads from the environment by default and PG is configurable in the environment (if you have a password on your local DB for instance). So we opted for the simpler dev machine setup (no need to copy/pasta an example database.yml) since connection credentials can live in the environment instead of that file.Also, Heroku allows for configuring ActiveRecord via
database.yml(https://devcenter.heroku.com/articles/rails-database-connection-behavior#configuring-connections-in-rails-4-1) so ignoring it would prevent this kind of configuration, right?