Providing Virtual Subhosts with Miva
To provide Virtual Subhost with Miva support, we recommend that you use
configuration directive in the miva.conf
- Be sure that the following parameters are set in miva.conf:
| NOTE: If you
choose to set
then your miva.conf
must have a
directive for each of the virtual subhost's domain names. For
example, using 'HTTP_HOST'
will require both subhost-domain.com and www.subhost-domain.com
to have its own
directive in miva.conf.
This is why we recommend using 'SERVER_NAME'
instead, because in your httpd.conf, you can consolidate a virtual
subhost's multiple host names under a single
directive with just one
This is documented in the instructions below.
- Add the
directive to miva.conf.
Assuming that you are using
in miva.conf, the name
should equal the
for the subhost defined in the
directive for your web server in your httpd.conf
parameter should equal the virtual subhost's
(another parameter of the
directive in httpd.conf).
should be outside of the ~/www/htdocs
directory, unaccessable by others, since all data collected by Miva
will be stored in that directory.
The VirtualHost directive in miva.confshould
look something like this:
- You may or may not need to modify your web server configuration file,
httpd.conf, depending on the method you are using to give your virtual
subhost's CGI support. After ensuring that the parameters defined in
directive in httpd.conf
matches those you set in the
directive of miva.conf,
you must check if your subhost has access to the Miva engine that was
put in your ~/www/cgi-bin
during the Miva installation.
If the virtual subhost is sharing your virtual server's primary cgi-bin
directory--meaning that you have not explicitly identified an alternate
for the subhost in the
directive of httpd.conf--then
after following all the instructions above, Miva should be setup and
ready to support your virtual subhost. If you don't understand what
is, then your virtual subhost is probably using your primary cgi-bin
directory and the Miva engine therein, so you don't have to worry about
making anymore changes. Go on to the next step.
However, if the virtual subhost has its own cgi-bin directory,
then we would recommend that you give that virtual subhost access to
the Miva engine in your primary cgi-bin directory by adding the following
to your httpd.conf's
| NOTE: If Miva
still has problems running an application for a virtual subhost,
or runs the application but stores data in the wrong directory,
then delete all the files in your
(the default installation will have this set as ~/www/miva/workdir).
This directory contains a caching database with virtual subhost
configuration information. Deleting the database files will
require Miva to reload the new
information from miva.conf.