Well,
We have several developers all with their own server and applications. They
check everything into one version control, which routinely gets uploaded to
the one production server. This production server has several vhosts
running on it. There is no way to set contexts on the development servers
and have all the links work properly, so what we have to do is create cnames
for each site and dev box. For example, for the first developer, we have
site1-dev1, site2-dev1, etc. For another developer we have site1-dev2,
site2-dev2, etc. That way the developers do not have to change contexts
every time they want to work on a different "virtual site" on their dev
machine. There are a couple possible solutions, but this seems to work
best.
-----Original Message-----
From: Mark Mynsted [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 26, 2001 11:53 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: Setting Contexts to work like vhosts
Ok. How did you do it?
Sincerely yours;
Mark Mynsted
VHA Management Information Systems Client Services
[EMAIL PROTECTED]
(972) 830 - 0592, Internal x1592
>>> [EMAIL PROTECTED] 4/26/2001 11:43:36 AM >>>
Just in case anyone was wondering, I got the problem solved. If anyone else
runs into a similar problem, I can help out.
Brandon
-----Original Message-----
From: Brandon Cruz [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 26, 2001 9:30 AM
To: [EMAIL PROTECTED]
Subject: Setting Contexts to work like vhosts
I am trying to figure out a way to set contexts so that they will work like
virtual hosts (as far as the root directory and everything goes). The
reason I can't use vhosts is because it is a development machine.
Basically, I want my links to work properly on the development machine, and
when I switch them to production on an actual virtual host. Is there a way
to accomplish this?
Thanks!
Brandon
