Because for local development we're using the unix username to connect to postgres, rbates in your case, you can simply ommit both username and password from database.yml. The underlying library will default to that user name. That way other developers working on the same project can use the same database.yml.
When you specified the postgres URL for taps, you could've also taken advantage of the fact that it's using the default username and host to connect to postgres. The URL can therefore be merely: postgres:///store_development.
Finally, check out valkyrie, the likely successor of taps.
Really glad to see postgres covered here!
A couple of tips:
rbates
in your case, you can simply ommit bothusername
andpassword
from database.yml. The underlying library will default to that user name. That way other developers working on the same project can use the same database.yml.postgres:///store_development
.Finally, check out valkyrie, the likely successor of taps.
Thanks!