Since I develop on one platform and my production servers will be on
another, I use virtualization a lot. You can use Microsoft Virtual PC,
or VMWare''s products. I am using Microsoft''s Virtual Server,
which has
a free download, and a 180 day evaluation license. Despite the name, it
runs on Windows XP too.
With enough memory, I can run a QA system, or a full production
simulation - multiple web server, multiple app servers, database
servers. Just don''t run any performance tests!
The problem with trying to run a QA system on the same box as a dev
configuration is that, with all these GEM_HOME and other configurations,
is this really the same as the QA or production machine is running? The
further away you get from what you want, the less useful the process
becomes.
-----Original Message-----
From: Matthew Beale [mailto:mixonic-8rZIAEcCR/xWk0Htik3J/w@public.gmane.org]
Sent: Friday, December 23, 2005 6:25 AM
To: rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
Subject: Re: [Rails] Maintaining a Dev and a QA environment
On Fri, 2005-12-23 at 08:38 -0500, Kevin Bedell wrote:> Has anyone seen any docs on how to maintain multiple environments on
the same> machine? Specifically, I''m wondering how I can maintain a
"dev" and a
"qa"> environment on the same machine.
>
> I want to be able to have "qa" match the production environment
in
terms of> which gems and with versions of the gems it has while upgrading the
> gems in the
> dev environment on a different schedule. That way I could, for
example, > keep dev
> up to date with the latest rails gems while not upgrading the qa
environment> until I''m testing for a release.
>
> Using Java this is pretty easy in terms of environments - you simply
set a> "JAVA_HOME" which defines the jdk you''re using and then
you include
whichever> versions of the jar files you need in the classpath for each
environment.
http://docs.rubygems.org/read/chapter/3#page13
GEM_HOME looks like it can tell ruby to use a specific location for
gems. You could set it separately for each "environment" in the
webserver''s exported variables. But you''d need to maintain
several gem
repositories.
Or make use of freeze_gems and such as David suggested.
-Matthew Beale
mixonic-8rZIAEcCR/xWk0Htik3J/w@public.gmane.org :: 607 227 0871
Resume and Portfolio @ http://madhatted.com
_______________________________________________
Rails mailing list
Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
http://lists.rubyonrails.org/mailman/listinfo/rails
