As indicated above, there are three ways to define an application
in Chili!Soft. Because two of these methods take information from
the httpd.conf file, these methods can be turned on or off
within the casp.cnfg file. The use of |
directories as applications is discussed in the section "Chili!Soft
and Virtual Subhosts" below. Controlling whether aliases from
your httpd.conf file are included as applications can be
done in the
[applications] section of the casp.cnfg
configuration file is located in the ~/usr/local/casp/asp-apache-3000/
directory of your Virtual Private Servers, and is called casp.cnfg.
This contains a number of changeable settings that control how your
ASP server behaves.
Do not change any values in the
section of the casp.cnfg file. Any changes to this
section will cause your ASPs to stop functioning.
The last section
of the casp.cnfg file is labeled
and includes a list of all the directories other than http aliases
and document roots where ASPs will run. The default casp.cnfg
[applications] section similar to this:
The second configuration
command above in the
[applications] section is the
value to tell Chili!Soft to use the aliases in the httpd.conf
as applications or not. By setting it to
Aliases listed in your httpd.conf file will
not be areas where ASPs will run.
tells where additional applications can be listed. The file indicated
(.aspconf) must be located in your primary
directory. Adding and removing applications from the .aspconf
file does not require you to shut down and restart your ASP engine
or the Web server. This allows you to quickly and easily add or
remove application locations.
listed after the config_name setting are application definitions,
following the format
Most of the
applications listed here are sample applications. An application
name is treated by the Web server as the same as an Alias listed
in the httpd.conf file. In other words, to access the
application, you would use your primary domain name and follow the