Global Configuration File
The logical name VWCMS_CONFIG locates the system global configuration file. For example
To make this permanent the name would need to be defined during system startup. Do not have this located within the VWcms application directory tree or it may be lost at the next VWcms update. It is best located in the suggested VWcms sites root.
VWcms configuration occurs in two phases. The global configuration file is loaded first, then any site configuration file. By default site configuration files are _VWCMS.CONF located in the VWcms site directory. Global directives cannot be used in a site configuration file. Site directives can be used in the global configuration file where they can configure site characterstics globally, or per-site by selective application using conditional configuration. If required these characteristics can then be overridden by a subsequently loaded site configuration file. This approach allows the system adminstrator to set VWcms policy for the site in a way that cannot be overridden by VWcms site administrators who can and should be able to set configuration parameters for their own sites.
Much of the flexibility in configuring VWcms sites is derived from the conditional application of directives based on specific request characteristics as represented by CGI variables. Condition testing is done via "*" wildcard match (matches any zero or more characters) or using regular expression matching (prefix the term with a ^ character). For example, the regular expression
would match a request to any service at example.net and configure it with the enclosed directives. The equivalent wildcard match
would match www.example.net and sales.example.net and products.example.net but not example.net.
An equivalent configuration based on request path
Conditionals may be nested and each must be terminated using an [if-end].
The following table describes the available conditional directives.
These conditional directives are also available for site configuration.
These are used to determine overall site charactersictics, especially the location in the file system. Global directives cannot be used in a site configuration file. Directives are case-insensitive.