[Question] Why does rails4.rb prevent the creation of database.yml? about heroku-buildpack-ruby HOT 8 CLOSED

Rails 4 is supposed to support a DATABASE_URL environment variable out of the box, so writing a database.yml should no longer be required, however there has been some back and forth on the code in question.

from heroku-buildpack-ruby.

@schneems do you know if Rails 4 prefers that DATABASE_URL? If not, then if you had a preexisting database.yml with the default production.sqlite3 in the production: setting that it would be bad... make sense? I don't currently have a Rails 4 app up on Heroku yet though to see.

from heroku-buildpack-ruby.

Can you provide specific issues you're seeing here? What isn't working? Stacktraces? Commands run?

Thanks.

from heroku-buildpack-ruby.

@hone Upon reading this thread, I realized that it was probably my fault. I double checked, and the problem was actually that the pg addon doesn't give db:reset privileges, which I interpreted to mean that my database connection from rails was failing. It appears to work fine now, so I'll close this out.

from heroku-buildpack-ruby.

This is quite annoying. I have a worker script in my rails 4 app that loads active record and connects to my heroku postgres without loading rails. I spent quite a few minutes banging my head against the wall before finding this issue and forking the buildpack for a quick fix. Perhaps this new behavior could be opt-in?

from heroku-buildpack-ruby.

Hey @gkop, you should be able to load your current database connection from the DATABASE_URL environment variable with ActiveRecord::Base.establish_connection, were you trying that or trying to read from database.yml?

from heroku-buildpack-ruby.

Hi @catsby.

This complained that I didn't specify an adapter:

ActiveRecord::Base.establish_connection(ENV['DATABASE_URL'])

And this didn't respect the url:

ActiveRecord::Base.establish_connection(adapter: "postgres", url: ENV['DATABASE_URL'])

Using Rails from git rails/rails@b5e4eb2.

My web dyno, where I load rails, is perfectly happy... it's the worker dyno, where I use active record on its own, that I miss database.yml.

from heroku-buildpack-ruby.

ah, my mistake, I recall that being in issue in at least rc1.

from heroku-buildpack-ruby.