[Xitami] HELP - virtual DNS hosting
John Jonas
xitami@lists.xitami.org
Thu, 20 Sep 2001 20:52:14 -0500
Russel Olinger wrote:
> I assumed you used the wizard to add the VH. When you created:
>
> [Server]
> Cgi-bin=e:\webhome\cgi-bin
> Webpages=e:\webhome\audctrl
Probably, it is has been so long ago I don't remember, but my guess is that you
could do it with notepad and then stop and restart xitami.
> Did Xitami automatically create the images, private and xitami
> subdirectories in the \webhome\audctrl directory? And is it creating the
> necessary files that go into the directories (such as those you would find
> the /htdocs/xitami directory)
There is 1 subdirectory under e:\webhome\audctrl and I created it manually.
Under e:\webhome\arbor there is a \images subdirectory but I think I created it
and the other subdirectories were definately my creations. I know of nothing
being automatically create in e:\webhome\audctrl.
> I am trying to keep everything related to a VH
> consolidated to a single directory that would like this:
<snip>
I'm deliberately using a common cgi, ftp, etc., but what you propose should
work, if you manually create the subdirectories and edit the virtualhost.cfg
file accordingly. In my installation there are cgi-bin, doc, images, pcnadmin,
pcntest, session, and xitami subdirectories under e:\webhome that were created
by the xitami install.
FYI: t:\ftphome is on a physically separate machine. The drive t: is a mapped
network share to another machine. I do not run xitami as a service, thereby
allowing the connection to t: to occur before xitami is manually started (I
think this could be done automatically as a service, but starting xitami
manually is not a problem either and xitami doesn't get in the way if I doing
other maintenance on that box).
> Last question, do you have to create any kind of alias mapping (aside from
> the host-vhx.cfg file) using the "Aliases" or "VHosts" sections. I would
> think you don't but then again I thought this process would be easier.
Only thing I know of is the contents of the 2 .cfg files.