Bundler.require_env

3 views

Skip to first unread message

Ken Collins

unread,

Nov 11, 2009, 9:44:30 PM11/11/09

to Ruby on Rails: Core

So I'm playing with an existing 2.3.4 app on edge and had a question about the bundler. First, I have already made all the changes to the app's boot, application, environment, and any other files so that it matches a current newly generate 3.0.pre rails app. I have also removed all my config.gem entries and built a nice little Gemfile. So here are a few silly questions.

If I do not run "gem bundle", and boot.rb does its "Use 2.x style vendor/rails and RubyGems", is there a preferred way that the Gemfile is supposed to work with the Rails.env to do what config.gem did? For instance if the Gemfile specifies shoulda only in test and I'm not "bundling", can the app fail to load and/or require shoulda? I looked at placing Bundler.require_env(Rails.env) at the top of my test.rb, but that is not working and I'm not even sure if that is the way to go.

That aside, I'm even having an issue bundling a vanilla rails edge to even load. I've tried all flavors of adding things to the Gemfile including options like below and even adding some lines for arel 0.2.pre, all to no avail. I realize this might be a premature question, but does anyone have any advice?

gem "rails", "3.0.pre"
gem "rails", :git => "git://github.com/rails/rails.git"
gem "rails", "3.0.pre", :git => "git://github.com/rails/rails.git"