Platform Team/Server Kit/Mace: Difference between revisions
| Line 37: | Line 37: | ||
In addition to configuration files, Mace can process files with a {{Code|.env}} suffix. These files contain variable declarations in Bash syntax. The values of these variables might be entered in configuration files in the form of {{Code|@VARIABLE@}}, in which case they will be expanded to real values while applying the configuration. | In addition to configuration files, Mace can process files with a {{Code|.env}} suffix. These files contain variable declarations in Bash syntax. The values of these variables might be entered in configuration files in the form of {{Code|@VARIABLE@}}, in which case they will be expanded to real values while applying the configuration. | ||
=== Keywords === | |||
Source configuration file names might contain substrings in format | |||
[''keyword''] | |||
that will say Mace that this source file can be processed only if this particular keyword is enabled in Mace by mentioning keyword name in {{Code|--keywords}} command-line argument. | |||
By default, Mace contain these keywords enabled: | |||
* ''production'' | |||
For example if there is a sources tree: | |||
<dir> +squid.d | |||
<config> | +010.base.conf | |||
<config> | +020.log[production].conf | |||
<config> | +020.log[test].conf | |||
The final configuration tree will be: | |||
<dir> +squid.d | |||
<config> | +010.base.conf | |||
<config> | +020.log[production].conf | |||
== Configuration application == | == Configuration application == | ||