If you had the sqlite gem in your Gemfile, Heroku should have installed it for you. Not sure why it didn't.
Regardless, though, Heroku provides each app with a Postgres database, which is more fully-featured than sqlite, so it would be a good idea to get used to using it instead. It's a good rule to keep your development and production environments the same, so you'll probably want to install Postgres locally as well. All that said, it's totally fine if you want to wait a while to jump ahead to Postgres. Rails ships with sqlite because it's simple and easy to get started with (even though Heroku doesn't really support it). If you're just getting your feet wet with Rails you might want to wait before adding any more complexity - if you want to get this app in production quickly so that other people can play with it, though, you should probably jump ahead to Postgres. On Nov 27, 12:43 pm, Roy Pardee <[email protected]> wrote: > On Nov 27, 10:06 am, Roy Pardee <[email protected]> wrote: > > > > > > > > > > > Hey All, > > > I'm trying to put up a very simple rails3 app, and seem to be stuck at > > the rake db:migrate step with a "no such file to load -- sqlite3". > > That's an error I'm used to saying when setting up a new windows > > computer for rails work--got to put the sqlite3.dll on the path for it > > to work. But it seems odd that heroku wouldn't have the proper sqlite > > stuff available. Can anyone advise? > > > Many thanks! > > > -Roy > > > Here's the barf in question: > > > $ heroku rake db:migrate > > rake aborted! > > no such file to load -- sqlite3 > > /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.3/lib/bundler/ > > runtime.rb:64:in `require' > > /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.3/lib/bundler/ > > runtime.rb:64:in `block (2 levels) in require' > > /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.3/lib/bundler/ > > runtime.rb:62:in `each' > > /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.3/lib/bundler/ > > runtime.rb:62:in `block in require' > > /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.3/lib/bundler/ > > runtime.rb:51:in `each' > > /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.3/lib/bundler/ > > runtime.rb:51:in `require' > > /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.3/lib/bundler.rb: > > 112:in `require' > > /disk1/home/slugs/361339_413858d_dbb1-98c85f12-e88f-48d0- > > b7e6-3a16c5098bf4/mnt/config/application.rb:7:in `<top (required)>' > > <internal:lib/rubygems/custom_require>:29:in `require' > > <internal:lib/rubygems/custom_require>:29:in `require' > > /disk1/home/slugs/361339_413858d_dbb1-98c85f12-e88f-48d0- > > b7e6-3a16c5098bf4/mnt/Rakefile:4:in `<top (required)>' > > /usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:2373:in `load' > > /usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:2373:in `raw_load_rakefile' > > /usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:2007:in `block in > > load_rakefile' > > /usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:2058:in > > `standard_exception_handling' > > /usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:2006:in `load_rakefile' > > /usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:1991:in `run' > > /usr/ruby1.9.2/bin/rake:31:in `<main>' > > (in /disk1/home/slugs/361339_413858d_dbb1-98c85f12-e88f-48d0- > > b7e6-3a16c5098bf4/mnt) > > > r...@zoidberg /c/railsapps/pardee_santa (master) > > After posting I continued flailing about and eventually got it to work > after migrating it to bamboo-ree-1.8.7 by commenting-out the line > > gem 'sqlite3-ruby', :require => 'sqlite3' > > in my Gemfile. This breaks the app for local use, but seems to fix it > for heroku. > > No clue whether that fix would have also fixed it on bamboo-mri-1.9.2. > > Cheers, > > -Roy -- You received this message because you are subscribed to the Google Groups "Heroku" 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/heroku?hl=en.
