ansaurus

Question

Answer 1

A:

Ruby 1.9 isn't yet supported on heroku. Try to live with 1.8.7 (for example, downgrade a little your sqlite3 gem).

Nikita Rybak 2010-10-03 03:12:41

I'm not sure about the problem that @elmany is running into, but I've bene using 1.9.2 and Rails 3.0 exclusively for the last couple of weeks with Heroku and things have worked just fine. The only time I had to reverte back to 1.8.7 was when doing a db:pull.

Joost Schuur 2010-10-03 09:04:09

@Joost Strange, maybe heroku page I refer to is outdated. Can't tell, as I run rails 2 only.

Nikita Rybak 2010-10-03 09:37:50

Yes, Heroku now support Ruby 1.9.2. But not at the time I tried to push. Also, for production one must forget about sqlite and use pg

elmany 2010-10-18 05:11:59

Answer 2

+1 A:

You want to use the sqlite3-ruby gem, not the sqlite3 gem.

Ryan Bigg 2010-10-03 05:21:25

I second this answer; the error you described is exactly what happens when you try to push to Heroku with `gem 'sqlite3'` in your Gemfile. Replace it with `gem 'sqlite3-ruby', :require => 'sqlite3'`, do a `bundle install`, commit, and push again.

BinaryMuse 2010-10-03 19:09:09

Answer 3

A:

Do you really mean to install sqlite on Heroku? Shouldn't that gem be limited to your development environment only, not production? You can't do much with sqlite on Heroku seeing how you can't write to the filesystem, nor can you specify a custom database (Heroku fully manages your database setting on pushed apps).

tfe 2010-10-03 05:39:25

Heroku is smart enough to ignore sqlite on the production environment. You can use it for local development and don't have to do anything special with your Gemfile to trigger it to be ignored or excluded in production there. They will even ignore your database.yml's production block and automatically use PostgreSQL. Their read only file system makes it impossible to use sqlite anyway.

Joost Schuur 2010-10-03 09:06:22

Answer 4

+1 A:

You're going off on the wrong path - Heroku doesn't run Sqlite, it runs PostgreSQL. When you deploy your app it creates a new database.yml file for you. So you shouldn't specify Sqlite in your gemfile - you should only specify it for your development environment.

Something like this:

group :production, :staging do
  gem "pg"
end

group :development, :test do
  gem "sqlite3-ruby", :require => "sqlite3"
end

If you want to read more about Heroku database stuff, go here. I asked a similar question (and got my answer) here.

Jaco Pretorius 2010-10-10 20:07:11

Hi, I follow your recipe and it worked. Thanks.

elmany 2010-10-18 05:09:26

Answer 5

A:

The reason 1.8.7 is showing up in your log is that is the default ruby version on heroku. If you want to use 1.9.2, see the doc on switching stacks: http://docs.heroku.com/stack

tee 2010-10-22 05:41:20

ansaurus

tags:

views:

answers:

Problem pushing a master to heroku

related questions