Configuring modules
How a module can be configured depends on what module it is. Each
module contains its own set of configuration options. However, there
are some options that are available for all modules.
Status and debug info
Status and debug info shows specific information about the
usage of that module. This option exists for modules that provide this
extra information.
Builtin variables
The builtin variables are available for all modules, but the number of
builtin variables vary dependent on the type of the module. The
possible builtin variables are:
- Comment
-
The Comment variable makes it possible
to write a comment about this module, that can be seen by anyone
having access to the configuration interface.
- Module name
-
The Module name variable makes
it possible to rename the module in the configuration interface.
- Priority
-
The priority of a module determines which
module gets to handle a request, when there are several modules of the
same type enabled. The module with the highest priority gets to try
first. In case that module failed to handle the request, the module
with the next highest priority gets to try. This continues until a
module is found that can handle the request, or all modules of that
type has been tried.
If two modules have the same priority it is not defined who gets to
handle the request.
- Security: Patterns
-
The Security: Patterns
variable determines who gets to access this module. It is possible to
limit access to certain computers, networks or users. See the Security considerations chapter for more
information.
- Security: Realm
-
In case access to the module is
limited to certain users this variable will be used when asking for
the user name and password. It will usually show up on the password
dialog shown by the web browser.
- Security: Security level
-
The Security: Security
level variable determines which other module may be part of
serving the request. This is usually usable in case you only trust
some users to use certain modules, for example the Pike
tag module. By giving the Filesystem module
serving pages from untrusted users a lower security level than the
Pike tag module it will not be possible for them to
write pages that use the <pike> tag.
More information about security level can be found on the trust levels page of the security considerations chapter.
|