I wish I had a hard-and-fast answer for you Johnny, but one question that comes to mind: is the staging environment somehow "inheriting" settings from your test environment?
On Apr 18, 2:49 am, johnnybutler7 <johnnybutl...@gmail.com> wrote: > thanks, > > my gem file is: > > source 'http://rubygems.org' > > gem 'rails', '3.0.3' > gem 'omniauth' > gem 'pg', :require => 'pg' > gem 'devise' > gem 'cancan' > gem 'haml' > gem 'hpricot' > gem 'ruby_parser' > gem 'rails_admin', :git => 'git://github.com/sferik/rails_admin.git' > gem 'acts-as-taggable-on' > gem 'jquery-rails' > gem "will_paginate", "~> 3.0.pre2" > gem 'factory_girl_rails' > gem "paperclip", "~> 2.3" > gem 'formtastic', '~> 1.2.0' > gem 'sunspot_rails', '1.2.1' > gem 'omniauth' > gem 'fb_graph' > gem 'recaptcha', :require => 'recaptcha/rails' > gem "friendly_id", "~> 3.2.1" > > group :development do > gem "nifty-generators" > end > > group :test do > gem 'test-unit' > gem "shoulda" > gem "rspec-rails", "2.0.0.beta.12" > gem 'cucumber-rails' > gem 'pickle' > gem 'capybara' > gem 'database_cleaner' > # gem 'webrat' > # gem 'webrat', '>=0.7.2.beta.6', :git => 'git://github.com/ > orangewise/webrat.git' > gem 'capybara' > gem 'factory_girl_rails' > gem 'ZenTest' > gem 'redgreen' > gem 'autotest-rails' > gem 'autotest' > gem 'autotest-fsevent' > gem 'autotest-growl' > gem 'autotest-notification' > gem "email_spec" > gem "launchy" > gem "Selenium" > gem "selenium-client" > gem "database_cleaner" > gem 'mongrel', '>= 1.2.0.pre2' > gem "fakeweb", ">= 1.2.5" > end > > When i do a rake db:migrate RAILS_ENV=staging > > Could not find autotest-fsevent-0.2.4 in any of the sources > Try running `bundle install`. > > Baffling! > > On Apr 16, 4:50 am, Bryan Crossland <bacrossl...@gmail.com> wrote: > > > > > > > > > Sent from my iPhone > > > On Apr 15, 2011, at 8:01 AM, johnnybutler7 <johnnybutl...@gmail.com> wrote: > > > > Hi, > > > > I have gem file set up so only the specific gems are installed/needed > > > for each environment, so all the test gems like cucumber etc are > > > grou[ed in test. When i try a rake db:migrate RAILS_ENV=staging on > > > the staging server however i get an error saying XXXX gem is not > > > installed, please use bundle install. I dont want the test gems > > > installed on this server however when i run the migration on staging > > > its expecting them to be installed. > > > > Anyone hit this problem before and how did you sort it, i cant find > > > anything in the forums? > > > Could you post your Gemfile and the error you're getting? It might be in > > the way the Gemfile is written. Also, make sure that whatever gem is > > failing is not being required some where else in your app. > > > B. -- 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 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.
