Sets the size of the internal page cache, where size is the number of byte-compiled pages to be cached for future use. Default is MaxRequestsPerChild / 5, or 50, if MaxRequestsPerChild is 0.

Tcl script that is run when each interpreter is initialized. script is an actual Tcl script, so to run a file, you would do:

Script to be evaluated when each Apache child process is initialized. This is the recommended place to load modules, create global variables, open connections to other facilities (such as databases) and so on.

Script to be evaluated when each Apache child process exits. This is the logical place to clean up resources created in ChildInitScript.

Script to be evaluated before each server parsed (.rvt) page. This can be used to create a standard header, for instance. It could also be used to load code that you need for every page, if you don't want to put it in a GlobalInitScript ChildInitScript when you are first developing a web site.

Script to be called after each server parsed (.rvt) page.

When Rivet encounters an error in a script, it constructs an HTML page with some information about the error, and the script that was being evaluated. If an ErrorScript is specified, it is possible to create custom error pages. This may be useful if you want to make sure that users never view your source code.

Directory to place uploaded files.

Maximum size for uploaded files.

This option controls whether it is possible to upload files to a Tcl variable. If you have a size limit, and don't have to deal with large files, this might be more convenient than sending the data to a file on disk.

If on, Rivet will create a seperate Tcl interpreter for each Apache virtual host. This is useful in an ISP type situation where it is desirable to seperate clients into seperate interpreters, so that they don't accidentally interfere with one another.