How to use postgres with rails on heroku

Question

I am having the following contents in a database.yml

production:
  adapter: postgresql
  database: dbname
  host: host.compute-1.amazonaws.com
  username: user
  password: pass_word
  DATABASE_URL: postgres://user:[email protected]:5432/dbname

However on a git push heroku master, I am getting the following error.

could not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5432?

Do I need changes for other environments as well?

I have added it only after getting the error earlier, but without any change in error — Sumit Bisht
– Sumit Bisht, Commented Jul 18, 2013 at 6:55
you got the error while git push so can you please paste the total errors which you got while git push heroku master — Rajarshi Das
– Rajarshi Das, Commented Jul 18, 2013 at 6:58
Please also check stackoverflow.com/questions/16124490/… and also check config.assets.initialize_on_precompile = false — Rajarshi Das
– Rajarshi Das, Commented Jul 18, 2013 at 7:00

Debadatt · Accepted Answer · 2013-07-18 07:00:01Z

3

heroku autogenerates database.yml on the deploy.

You need to .git ignore database.yml

You may choose another database by setting the ENV['DATABASE_URL'] (use heroku config:add DATABASE_URL=....)

For more information please check the heroku documentation

answered Jul 18, 2013 at 7:00

Debadatt

6,0134 gold badges30 silver badges40 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Amrit Dhungana · Accepted Answer · 2013-07-18 06:57:12Z

0

DATABASE_URL is not required. Or you can check this one http://railsapps.github.io/rails-heroku-tutorial.html

answered Jul 18, 2013 at 6:57

Amrit Dhungana

4,5035 gold badges35 silver badges36 bronze badges

1 Comment

Rajarshi Das Over a year ago

Please see our comments

Neil Middleton · Accepted Answer · 2013-07-18 15:17:38Z

This error

could not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5432?

is emitted during push, because be default Rails will spin up to precompile assets, and part of that is Rails trying to connect to the database. During build time, your application configuration is not present, hence why Rails tries to fall back to the default of using localhost (which doesn't exist).

There's a couple of ways to stop this happening. One (the recommended way) is to set

config.assets.initialize_on_precompile = false

in your production.rb.

A second way, is to enable the user-env-compile labs feature that will allow your PG config to exist at build time.

$ heroku labs:enable user-env-compile -a <YOUR_APP_NAME>

Collectives™ on Stack Overflow

How to use postgres with rails on heroku

3 Answers 3

Comments

1 Comment

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related