Configuration Import and Export

The Management UI provides configuration import and export functionality for transferring complete configuration packages as ZIP archives. Official example configuration ZIP packages are published to the radiator-radconfs GitHub repository.

The import and export features are useful for creating backups, sharing configurations with support, or deploying example configurations from external sources.

Accessing Import and Export

In the Management UI, navigate to Configuration -> Files. Click the menu button (...) in the upper right corner to access the import and export options:

• Import (.zip) - Upload a configuration archive
• Export (.zip) - Download the current configuration

To upload individual files (such as a single .radconf, certificate, or Lua script), use the Create button and select Upload file.

Configuration Export

Export creates a ZIP archive containing the current configuration. If a pending configuration exists, the pending version is exported; otherwise the active configuration is exported.

Export Options

The export dialog allows selecting which content directories to include in the archive:

Internal directories (pending/, backups/, and snapshot metadata) are always excluded from exports.

Common Export Use Cases

Creating a backup: Export with default options to create a backup of your configuration files, certificates, databases, and Lua scripts.

Sending configuration to support: When requesting assistance from the Radiator support team, export the configuration and send the ZIP archive. Consider excluding licenses and management credentials unless specifically requested.

Configuration Import

Import extracts a ZIP archive into the pending configuration directory. After import, review the changes in the Management UI and apply them to activate the new configuration.

Import Options

The import dialog provides control over which content types to import from the archive:

Content that is not imported from the ZIP archive is automatically copied from the active configuration. This preserves existing settings for unchecked content types.

When a content type is enabled for import but the ZIP archive does not contain that directory, the directory will not be preserved from the active configuration. A warning is shown in this case.

Template and License Import Modes

Templates and licenses support three import modes:

• Append (default for templates) - Merge imported files with existing files. Imported files overwrite existing files with the same name.
• Replace - Delete all existing files and import only files from the ZIP.
• Ignore (default for licenses) - Keep existing files unchanged. Skip all files of this type in the ZIP.

Overwriting Pending Configuration

If a pending configuration already exists, you must confirm overwriting it before importing. The import process replaces the entire pending configuration.

Common Import Use Cases

Restoring a backup: Import a previously exported backup to restore configuration. Typically import with default options, then review and apply changes.

Deploying example configurations: Import example configuration packages from the radiator-radconfs GitHub repository. These packages provide ready-to-use configurations for common deployment scenarios.

Migrating between environments: Export from a development or staging environment and import into production. Exclude environment-specific content like management credentials.

ZIP Archive Structure

Configuration archives follow the standard Radiator configuration directory layout, e.g.:

radiator-config-YYYY-MM-DDTHH-MM-SSZ.zip
|-- *.radconf (configuration files)
|-- db/
|   `-- users.db
|-- tls/
|   |-- server.crt
|   `-- server.key
|-- lua/
|   `-- custom.lua

Configuration files (.radconf) are stored at the root level of the archive.

Template Import and Export

The Configuration -> Templates section provides dedicated import and export for template files only. This is useful when sharing or transferring templates independently from the rest of the configuration.

Accessing Template Import and Export

In the Templates view, click the menu button (...) in the upper right corner:

• Import templates (.zip) - Upload a ZIP archive containing template files
• Export templates (.zip) - Download all templates as a ZIP archive

To upload a single template file, use the Create button and select Upload template.

Template Import Options

When importing templates, select the import mode:

• Merge (default) - Add imported templates to existing templates. If a template with the same name exists, it is overwritten.
• Replace - Delete all existing templates before importing. Only templates from the ZIP are kept.

Template import creates a pending configuration if one does not exist. Review and apply the changes to activate the imported templates.

Excluded Files

The following files are automatically excluded from configuration operations:

• Internal management directories (pending/, backups/)
• Snapshot metadata files

These files contain runtime state that should not be transferred between environments.