database.yml:
# SQLite version 3.x #   gem install sqlite3 # #   Ensure the SQLite 3 gem is defined in your Gemfile #   gem 'sqlite3' development:   adapter: postgresql   encoding: utf8   database: sampleapp_dev  #can be anything unique   #host: localhost   #username: 7stud   #password:     #adapter: sqlite3   #database: db/development.sqlite3   pool: 5   timeout: 5000  # Warning: The database defined as "test" will be erased and # re-generated from your development database when you run "rake". # Do not set this db to the same as development or production. test:   adapter: postgresql   encoding: utf8   database: sampleapp_test  #can be anything unique   #host: localhost   #username: 7stud   #password:    #adapter: sqlite3   #database: db/test.sqlite3   pool: 5   timeout: 5000  production:   adapter: postgresql   database: sampleapp_prod   #can be anything unique   #host: localhost   #username: 7stud   #password:    #adapter: sqlite3   #database: db/production.sqlite3   pool: 5   timeout: 5000 pg_hba.conf:
# TYPE  DATABASE        USER            ADDRESS                 METHOD  # "local" is for Unix domain socket connections only local   all             all                                     trust # IPv4 local connections: host    all             all             127.0.0.1/32            trust # IPv6 local connections: host    all             all             ::1/128                 trust # Allow replication connections from localhost, by a user with the # replication privilege. #local   replication     postgres                                md5 #host    replication     postgres        127.0.0.1/32            md5 #host    replication     postgres        ::1/128                 md5 I changed the METHOD in the first three lines from md5 to trust, but I still get the error.
And no matter what combinations of things I try in database.yml, when I do:
~/rails_projects/sample_app4_0$ bundle exec rake db:create:all I always get the error:
fe_sendauth: no password supplied
I followed this tutorial to get things setup:
https://pragtob.wordpress.com/2012/09/12/setting-up-postgresql-for-ruby-on-rails-on-linux
Mac OSX 10.6.8 PostgreSQL 9.2.4 installed via enterpriseDB installer Install dir: /Library/PostgreSQL/9.2 After making changes to the pg_hba.conf or postgresql.conf files, the cluster needs to be reloaded to pick up the changes.
From the command line: pg_ctl reload
From within a db (as superuser): select pg_reload_conf();
From PGAdmin: right-click db name, select "Reload Configuration"
Note: the reload is not sufficient for changes like enabling archiving, changing shared_buffers, etc -- those require a cluster restart.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With