--- title: Configuration Actions description: Host provisioning, template engine, and system-level configuration. weight: 53 --- Configuration actions are used to provision the host and maintain system-level services. They rely heavily on the built-in template engine to generate declarative configuration files. ## The Template Engine {#template-engine} The Root framework uses `envsubst` (from `gettext-base`) to render templates. This allows you to use standard Bash environment variables directly within your configuration files. ### Template Conventions - **File Extension**: Templates typically use the `.template` extension (e.g., `crontab.template`). - **Variable Syntax**: Use `${VARIABLE_NAME}` or `$VARIABLE_NAME` to inject values. - **Auto-Discovery**: Many actions automatically look for templates in specific directories within the [Configs](/root/glossary#configs) repository. ### Rendering Helpers The `root_template.sh` library provides several helpers: - `root_template_render `: Renders a single file. - `root_template_render_directory `: Recursively renders an entire directory structure. - `root_template_crontab