Files
alakazam/examples/config-sets.yml
Danny Groenewegen d2473ca74a feat: add config-sets support
Adds support for a config-sets.yml file at the root path where named bundles
of app configurations (env, hooks, secrets) can be defined and activated
per-instance or per-group, eliminating duplication across instance configs.

- Config-sets are defined as top-level keys in config-sets.yml
- Activate a set in any instance or group alaka.yml with CONFIG-SETS: <name>: true
- Disable a set inherited from a group with CONFIG-SETS: <name>: false
- Merge priority: group < config-set < instance
- Warns when a config-set is enabled but not defined in config-sets.yml
- Warns when a config-set targets an app not listed in the instance config
- Adds examples/config-sets.yml with bbb and calendar config-set examples
2026-05-28 12:03:52 +02:00

30 lines
635 B
YAML

# config-sets.yml
# Place this file at your alakazam root path.
# Each top-level key is a named config-set containing per-app configurations.
# Activate a set in any instance .yml or alaka.yml:
#
# CONFIG-SETS:
# bbb: true
# calendar: true
#
# Disable a set inherited from a group alaka.yml by setting it to false:
#
# CONFIG-SETS:
# bbb: false
#
bbb:
authentik:
env:
APPLICATIONS:
BBB: https://nextcloud.example.com/apps/bbb
nextcloud:
initial-hooks:
- app install_bbb
calendar:
authentik:
env:
APPLICATIONS:
Calendar: https://nextcloud.example.com/apps/calendar/