Rails - Apr 2007 - Can Rails 1.1.6 and 1.2 coexist on the same server?

On 4/16/07, Long <long755-bJEeYj9oJeDQT0dZR+AlfA@public.gmane.org>
wrote:
>
>
> So I am still on Rails 1.1.6 but want to start planning for migration to
> 1.2.
> Before I go and install 1.2 over my 1.1.6 environment I want to make sure
> things will not get messed up.
>
> It seems like I can select a Rails version by specifying the
> RAILS_GEM_VERSION.
> Knowing Rails it is probably that simple but I just want to get
> confirmation that
> is indeed the case.
>
> TIA
>
> -- Long
> http://MeandmyCity.com/ - Find your way
> http://edgesoft.ca/blog/read/2 - No-Cookie Session Support plugin

IMO, this should be Rule #1 of Rails deployment basically everywhere:

rake rails:freeze:gems

I *always* have Rails installed into my vendor directory so I never have to
worry about this kind of problem. Then it''s very easy to have multiple
rails
sites running with differing versions.

Jason

--~--~---------~--~----~------------~-------~--~----~
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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

So I am still on Rails 1.1.6 but want to start planning for migration to 1.2.
Before I go and install 1.2 over my 1.1.6 environment I want to make sure
things will not get messed up.

It seems like I can select a Rails version by specifying the RAILS_GEM_VERSION.
Knowing Rails it is probably that simple but I just want to get confirmation
that
is indeed the case.

TIA

-- Long
http://MeandmyCity.com/ - Find your way
http://edgesoft.ca/blog/read/2 - No-Cookie Session Support plugin


--~--~---------~--~----~------------~-------~--~----~
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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Jason Roelofs wrote:
> On 4/16/07, Long wrote:
> >
> >
> > So I am still on Rails 1.1.6 but want to start planning for migration
to
> > 1.2.
> > Before I go and install 1.2 over my 1.1.6 environment I want to make
sure
> > things will not get messed up.
> >
> > It seems like I can select a Rails version by specifying the
> > RAILS_GEM_VERSION.
> > Knowing Rails it is probably that simple but I just want to get
> > confirmation that
> > is indeed the case.
> >
> > TIA
> >
> > -- Long
> > http://MeandmyCity.com/ - Find your way
> > http://edgesoft.ca/blog/read/2 - No-Cookie Session Support plugin
> 
> 
> IMO, this should be Rule #1 of Rails deployment basically everywhere:
> 
> rake rails:freeze:gems
> 
> I *always* have Rails installed into my vendor directory so I never have to
> worry about this kind of problem. Then it''s very easy to have
multiple rails
> sites running with differing versions.
> 
So basically freeze gems for version 1.1.6 then install version 1.2 ...

Thanks,

-- Long


--~--~---------~--~----~------------~-------~--~----~
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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Well, more like for each rails site, freeze the gems at the proper version (
1.1.6 it sounds like). Then, on your development box, freeze the 1.2 gems to
the site and work on porting. Then you just drop the new site in place,
complete with 1.2 and you know it works.

Jason

On 4/16/07, Long <long755-bJEeYj9oJeDQT0dZR+AlfA@public.gmane.org>
wrote:
>
>
> Jason Roelofs wrote:
>
> > On 4/16/07, Long wrote:
> > >
> > >
> > > So I am still on Rails 1.1.6 but want to start planning for
migration
> to
> > > 1.2.
> > > Before I go and install 1.2 over my 1.1.6 environment I want to
make
> sure
> > > things will not get messed up.
> > >
> > > It seems like I can select a Rails version by specifying the
> > > RAILS_GEM_VERSION.
> > > Knowing Rails it is probably that simple but I just want to get
> > > confirmation that
> > > is indeed the case.
> > >
> > > TIA
> > >
> > > -- Long
> > > http://MeandmyCity.com/ - Find your way
> > > http://edgesoft.ca/blog/read/2 - No-Cookie Session Support plugin
> >
> >
> > IMO, this should be Rule #1 of Rails deployment basically everywhere:
> >
> > rake rails:freeze:gems
> >
> > I *always* have Rails installed into my vendor directory so I never
have
> to
> > worry about this kind of problem. Then it''s very easy to have
multiple
> rails
> > sites running with differing versions.
> >
> So basically freeze gems for version 1.1.6 then install version 1.2 ...
>
> Thanks,
>
> -- Long
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---