Your first thought was correct. If you're using sqlite3 to support your app's DB you can't even do "rake db:migrate" without having sqlite3-ruby installed. My guess is that the either gem was already in place or you had a "config.gem 'sqlite3-ruby'..." line in your app's environment.rb and ran "rake gems:install" as part of the app port to the server.
On Sep 18, 6:21 pm, nb <[email protected]> wrote: > I've always thought the sqlite3-ruby gem is needed for Rails apps to > use SQLite3 databases, until the other day. > > I set up a VM running Ubuntu 9.0.4, 32-bit server edition with Rails > 2.2.2 to host an app I had written (by the way, the VM was > surprisingly easier to setup than the Mac it replaced). > > I had neglected to install the sqlite3-ruby gem on the VM, which I had > installed on the Mac, but my app runs just fine on the VM anyway. > What gives? > > If someone can enlighten me, I'd appreciate it. > > Thanks! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
