Note that there are some explanatory texts on larger screens.

plurals
  1. POHartl's Chapter 7 when pushing to heroku, "pg is not part of the bundle" but it is
    text
    copied!<p>So I'm going through Hartl's Tutorial on RoR and I'm at the <a href="http://ruby.railstutorial.org/chapters/sign-up#sec-deploying_to_production_with_ssl" rel="nofollow">end of chapter 7</a>. I'm trying to deploy to heroku. Everything up until the</p> <pre><code>heroku run rake db:migrate </code></pre> <p>step works, but that step gives me the error below. I ran <code>bundle install</code> several times and I'm not sure where my problem is. Also I can't access my heroku app online, even if I run <code>heroku create --stack cedar</code> and then <code>git push heroku</code>. It just gives me an application error when I go to my heroku app URL. </p> <p>I am currently running Postgres.app and my rails server is not deployed.</p> <p>Included is my <code>Gemfile</code> and <code>database.yml</code>. Feel free to look at the code at <a href="http://github.com/sambaek" rel="nofollow">http://github.com/sambaek</a></p> <p>Can someone help out? Thanks!</p> <h2>Terminal output</h2> <pre><code>heroku run rake db:migrate Running `rake db:migrate` attached to terminal... up, run.1 DEPRECATION WARNING: You have Rails 2.3-style plugins in vendor/plugins! Support for these plugins will be removed in Rails 4.0. Move them out and bundle them in your Gemfile, or fold them in to your app as lib/myplugin/* and config/initializers/myplugin.rb. See the release notes for more on this: http://weblog.rubyonrails.org/2012/1/4/rails-3-2-0-rc2-has-been-released. (called from &lt;top (required)&gt; at /app/Rakefile:7) DEPRECATION WARNING: You have Rails 2.3-style plugins in vendor/plugins! Support for these plugins will be removed in Rails 4.0. Move them out and bundle them in your Gemfile, or fold them in to your app as lib/myplugin/* and config/initializers/myplugin.rb. See the release notes for more on this: http://weblog.rubyonrails.org/2012/1/4/rails-3-2-0-rc2-has-been-released. (called from &lt;top (required)&gt; at /app/Rakefile:7) Connecting to database specified by DATABASE_URL rake aborted! Please install the postgresql adapter: `gem install activerecord-postgresql-adapter` (pg is not part of the bundle. Add it to Gemfile.) Tasks: TOP =&gt; db:migrate =&gt; db:load_config (See full trace by running task with --trace) </code></pre> <h2>Gemfile</h2> <pre><code>source 'https://rubygems.org' gem 'rails', '3.2.8' gem 'bootstrap-sass', '2.0.4' gem 'bcrypt-ruby', '3.0.1' group :development, :test do gem 'rspec-rails', '2.11.0' gem 'guard-rspec', '0.5.5' gem 'pg' # gem 'sqlite3' gem 'guard-spork', '0.3.2' gem 'spork', '0.9.0' gem 'factory_girl_rails', '1.4.0' end gem 'annotate', '2.5.0', group: :development # Gems used only for assets and not required # in production environments by default. group :assets do gem 'sass-rails', '3.2.5' gem 'coffee-rails', '3.2.2' gem 'uglifier', '1.2.3' end gem 'jquery-rails', '2.0.2' group :test do gem 'capybara', '1.1.2' gem 'rb-fsevent', '0.9.1', :require =&gt; false gem 'growl', '1.0.3' end </code></pre> <h2>config/database.yml</h2> <pre><code># postgresql development: host: localhost adapter: postgresql encoding: utf8 database: sample_app_development pool: 5 username: password: test: host: localhost adapter: postgresql encoding: utf8 database: sample_app_test pool: 5 username: password: production: adapter: postgresql encoding: utf8 database: sample_app_production pool: 5 username: password: # sqlite3 # development: # adapter: sqlite3 # database: db/development.sqlite3 # pool: 5 # timeout: 5000 # # Warning: The database defined as "test" will be erased and # # re-generated from your development database when you run "rake". # # Do not set this db to the same as development or production. # test: # adapter: sqlite3 # database: db/test.sqlite3 # pool: 5 # timeout: 5000 # production: # adapter: sqlite3 # database: db/production.sqlite3 # pool: 5 # timeout: 5000 </code></pre>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload