Ruby on Rails Monday, December 10, 2012

It seens like creating a gemset will solve your problem.


What I usually do is create a .rvmrc file on the root of my application with the content: "rvm 1.9.3@gemset_name --create" 
so everytime in enter the directory of my application the gemset that I specified at the .rvmrc file will be loaded.


2012/12/10 Jordon Bedwell <envygeeks@gmail.com>
On Mon, Dec 10, 2012 at 2:19 PM, Colin Law <clanlaw@googlemail.com> wrote:
> Post the output from
> gem list
>
> Also copy/paste here the output from bundle install.

Gonna have to agree, to me it sounds like you installed on
ruby-1.9.3-p327 instead of @global or @gemset_name.  I've ran into
issues if I haven't installed into a gemset.  Make sure you are either
in @global or in another gemset you create.  I actually prefer not to
use @global at all because it mucks up the isolation I use RVM for but
you can do whatever you please.

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.





--
Pedro Henrique de Souza Medeiros
----------------------------------
Cel: +55 (61) 9197-0993
Email: pedrosnk@gmail.com

Beautiful is better than ugly,
Explicit is better than implicit,
Simple is better than complex,
Complex is better than complicated.

The Zen of Python, by Tim Peters


--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

No comments:

Post a Comment