The latest Heroku stack requires postgres and will not allow SQLite at all ( I think it is called Cedars ) When you deploy, you will want to deploy on an older stack that allows SQLite. (I think Bamboo works with SQLite.) If you can deploy with SQLite, then you should not have any reconfigurations.
If you do end up having to deploy to postgres on Heroku you will have to make sure your Gemfile, database.yml, and possibly other files are adjusted to have SQLlite in the development environment and postgres in the production environment. At that point, you may find that your app performs differently in dev than production. If so, it is probably due to underlying nuances/differences in the two databases. Heroku STRONGLY recommends that you run postgres in your dev environment for just this reason. On Wednesday, February 8, 2012 3:00:45 PM UTC-7, Ruby-Forum.com User wrote: > > I am currently using MySQL as my database, I am guessing I will have to > re configure it all then? > > -- > Posted via http://www.ruby-forum.com/. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-talk/-/J0RSWfTcxkwJ. To post to this group, send email to rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
