Millscript has several levels of configuration. Which levels are used depends on the environment MillScript is used in. For instance the configuration available when using MillScript as an embedded system, via it's API is quite different from running a website script as a batch job.
MillScript has a certain amount of configuration information built-in. This includes information about the structure of a website folder, how verbose it should be and if debugging output is required.
In addition to the built-in configuration, we need to be able to set options such as how much memory MillScript is allowed to use and which version of MillScript should be used by default.
For more information on the different files and what directives they may contain, see the section on Configuration Files and Configuration functions.
The configuration file format is really quite simple and is a subset of MillScripts own syntax. The file is read as a sequence of expressions which are then evaluated. As currently implemented each expression must be an application of one of the documented configuration functions. Whitespace is completely ignored and end of line comments are supported(and discarded).
The available configuration functions are explained in the Configuration functions section.