Open rking opened 11 years ago
Asher, on #pry, explained that gem 'development'
shouldn't be
in the Gemfile
.
This still leaves the problem of how to make development.rb
work under
Bundler.
The problem is compounded by the way that you might cross ruby process
boundaries, e.g. how bundle exec guard
invokes spork
and rspec
as child
processes — totalling 3 executables (all hijacked by Bundler
).
So now I'm wondering if the trick isn't to:
gem 'pry-debundle'
Then call its API from config/application.rb
to allow access back to the
development
gem.
Yo Asher!
Having a bit of trouble.
gem 'development'
is in theGemfile
require 'development'
is above theBundler.require
fromconfig/application.rb
~/.development.rb
contains a mereputs 'TODO: get development.rb working'
Very next thing:
script/rails:6: stack level too deep (SystemStackError)
I haven't debugged this at all… but jotting this Issue so I don't forget about it.