Heroku: Why isn't the config/database.yml file relevant?

[Jason Hsu, Rubyist]

As you know, Heroku uses the PostgreSQL database by default.

However, when you deploy an app that you created with the use of SQLite in the development environment, the config/database.yml file on the Heroku server is still configured for SQLite.

Exactly how does Heroku make the config/database.yml file relevant?  How does the app get the database name, username, and password in the Heroku environment?

[Frederick Cheung]

On older rails versions heroku entirely rewrites the database.yml file. On rails 4.2 it doesn't need to because rails will use a DATABASE_URL environment variable if it is set. See https://devcenter.heroku.com/articles/heroku-postgresql#connecting-in-ruby for more details

Fred

[ANIL YADAV]

I think you need to changed your production configuration ...in your yml files...


production:
<<: *default
database: name_production
username: name
password: <℅= ENV['NAME_DATABASE_PASSWORD']℅>


the ENV tag automatic generated a unique password for your rail application on heroku production.... I am not confirm. Because I am also a new developer.

[ANIL YADAV]

[ANIL YADAV]