Whatever I can gather, Hrokok has to generate a database.iml file automatically, and ignore local To do. However, I am seeing an error where this is not true, and local databases. My changes in the field are affecting everyone's app. This is problematic because I do not know how to set up the file's setup production part so that Heroku could search the correct database.
For example, the following
Product: Adapter: sqlite3 Database: DB / Production. Sqlite3 pool: 5 timeout: 5000 After DB: Migration
$: ~ / apps / dancingcupid / dancingcupid $ heroku rake --trace db: migrate spits out
Rack aborted! Unable to open database file /app/.bundle/gems/ruby/1.8/gems/activerecord-3.0.5/lib/active_record/connection_adapters/sqlite3_adapter.rb:27:in 'start' ... ... Based on what type of database I've sent for production, I can get various errors.
In addition to removing the app and creating a new one, is there a way to fix this problem?
Haruku definitely modifies your database. Pushes the envelope, so no matter what the source control is in.
To ensure that the Horoku run bash will connect you to a session in your app, then do a cat config \ database.yml See more about how they wrote it.
Comments
Post a Comment