The only problem there is that your Gemfile.lock will be changing depending on who's making it, but that can be managed.
On Tue, Sep 13, 2011 at 08:53, Warren Seen <[email protected]> wrote: > +1 for this approach, have used it in the past too. Setting an env var is a > dead simple approach and doesn't force your whole team into the same working > directory setup. > On 13/09/2011, at 8:49 AM, Fred Wu wrote: > > We used something like this: > > https://github.com/stonean/slim/blob/master/Gemfile > > > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/rails-oceania/-/JpQF1R5DJskJ. > 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/rails-oceania?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" 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/rails-oceania?hl=en. > -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" 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/rails-oceania?hl=en.
