Interesting. I created an empty gemset, typed "gem list" and got:

*** LOCAL GEMS ***

rake (0.8.7)
rubygems-update (1.4.2)

So I started rails server and ran the app WITHOUT running bundle
install, and everything worked. This puzzled me. So I typed:

Sooper-2:Potluk Jasonp$ which ruby
/Users/Jasonp/.rvm/rubies/ruby-1.9.2-p136/bin/ruby

So far, so good. Then:

Sooper-2:Potluk Jasonp$ which rails
/usr/bin/rails

which, I'm assuming, is why it's running locally. Does that make
sense?

I assume I'm supposed to have a rails install WITHIN rvm somehow. I'm
going to try and figure out how to do that, and see if it runs
locally. If not, then I at least have two consistently broken versions
of my app, although if that's the case then I won't know why it isn't
running locally either. Sigh.



On Jan 30, 10:03 am, Oren Teich <[email protected]> wrote:
> You seem to be missing whatever provides "Digest".  Does it run locally if
> you create a blank gem set in RVM (rvm create 1.9.2@blank - make sure you
> don't have default gems by running gem list in that gemset).
>
> Oren
>
>
>
>
>
>
>
> On Sun, Jan 30, 2011 at 9:56 AM, Jason Preston <[email protected]> wrote:
> > Unfortunately it gives me the same error. I even went ahead and
> > commented the group :development blockin my Gemfile just in case there
> > was something I'm requiring for dev that is being left out of
> > production and breaking it...no dice.
>
> > Just for fun I tried migrating to 1.8.7 to see if it ran -- it does
> > not.
>
> > The logs produce the same output every time. Anything else I can
> > provide that would help determine what it's even looking for? It
> > boggles my mind that it runs locally - I don't even have ruby 1.9.1
> > installed...
>
> > On Jan 30, 8:43 am, Scott LaBounty <[email protected]> wrote:
> > > When I tried something similar, I didn't have much luck with migrating a
> > > stack. Try creating a new project with 1.9.2 initially and then your
> > push.
> > > That may work better.
>
> > > Scott
>
> > > On Sun, Jan 30, 2011 at 12:40 AM, Jason Preston <[email protected]>
> > wrote:
> > > > I've put the output from
>
> > > > $ heroku logs
>
> > > > on pastie for reference:  http://pastie.org/1511022
>
> > > > I have an app that runs beautifully on ruby 1.9.2 and rails 3.0.3 in
> > > > my local rvm environment, but after pushing to heroku and doing heroku
> > > > stack:migrate to bamboo-mri-1.9.2 my app will not start. I don't
> > > > really fully understand the output I'm getting from the logs,
> > > > especially given that it appears to be trying to load something from
> > > > ruby 1.9.1.
>
> > > > Has anyone seen this before? Any idea why the app is crashing on
> > > > heroku but running on local? I can't even tell what file it's trying
> > > > to load and not finding...and WHY is it trying to load 1.9.1 if I'm
> > > > running 1.9.2??
>
> > > > Any help would be much appreciated...
>
> > > > --
> > > > You received this message because you are subscribed to the Google
> > Groups
> > > > "Heroku" group.
> > > > To post to this group, send email to [email protected].
> > > > To unsubscribe from this group, send email to
> > > > [email protected]<heroku%[email protected]>
> > <heroku%[email protected]<heroku%252Bunsubscribe@googlegroups. 
> > com>
>
> > > > .
> > > > For more options, visit this group at
> > > >http://groups.google.com/group/heroku?hl=en.
>
> > > --
> > > Scotthttp://steamcode.blogspot.com/
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Heroku" group.
> > To post to this group, send email to [email protected].
> > To unsubscribe from this group, send email to
> > [email protected]<heroku%[email protected]>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/heroku?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Heroku" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/heroku?hl=en.

Reply via email to