Use YAML anchoring with multi-file configuration for modular, reusable configurations. Overview linkYAML anchoring allows you to: Maintain multiple configuration presets in separate files Switch between them instantly by changing one line Override specific fields when needed Keep your main config file clean and simple How It Works link info reference files must end with base file name like *-config.yaml. If your base file is config.yaml, your secondary files must be named server-config.yaml or frontend-config.yaml. The main config file uses YAML merge keys (<<:) to include anchored configurations from separate modular files: server-config.yaml - Server settings (port, sources, logging) auth-config.yaml - Authentication configuration integrations-config.yaml - Media and office integration settings frontend-config.yaml - UI styling and themes users-config.yaml - User default settings Basic Concepts link1. Anchor Definition (&anchor_name) linkDefine a reusable configuration block with a name. 2. Alias Reference (*anchor_name) linkReference the entire anchor exactly as defined. 3. Merge Key (<<: *anchor_name) linkMerge the anchor into the current context, allowing overrides. Quick Configuration Switching linkExample: Switch from development to production by changing the anchor reference: YAML Copy 1 2 3 4 5 6 7 8 9 # config.yaml - Switch environments by changing the anchor name # For development: server: <<: *server_dev # For production (just change the anchor name): server: <<: *server_production Example: Server Configurations linkFile: server-config.yaml YAML Copy 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 # Development server - multiple sources, verbose logging server_dev: &server_dev port: 8080 baseURL: "/dev" logging: - levels: "info|debug|warning|error" sources: - path: "/data/downloads" name: "downloads" - path: "/data/projects" name: "projects" # Production server - restricted sources, minimal logging server_production: &server_production port: 80 baseURL: "/" logging: - levels: "warning|error" sources: - path: "/data/public" name: "public" # Minimal server - single source server_minimal: &server_minimal port: 8080 baseURL: "/" sources: - path: "/data" File: config.yaml YAML Copy 1 2 3 4 5 # Simply change the anchor name to switch configurations! server: <<: *server_dev # Use development config # <<: *server_production # OR use production config # <<: *server_minimal # OR use minimal config To switch environments: Just uncomment the line you want! Example: User Permission Presets linkFile: users-config.yaml YAML Copy 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 # Admin user - full permissions user_admin: &user_admin showHidden: true permissions: admin: true modify: true share: true api: true # Regular user - standard permissions user_regular: &user_regular showHidden: false permissions: admin: false modify: true share: true api: false # Read-only user - view only user_readonly: &user_readonly showHidden: false permissions: admin: false modify: false share: false api: false lockPassword: true File: config.yaml YAML Copy 1 2 3 4 5 # Switch default user permissions with one line! userDefaults: <<: *user_regular # Use regular user settings # <<: *user_admin # OR use admin settings # <<: *user_readonly # OR use readonly settings Extending Anchors linkYou can also extend an anchor and add/override specific fields: File: server-config.yaml YAML Copy 1 2 3 4 5 6 7 8 9 10 server_base: &server_base port: 80 baseURL: "/" sources: - path: "/data" # Extend base and add search length server_extended: &server_extended <<: *server_base # Include everything from server_base minSearchLength: 10 # Add new field File: config.yaml YAML Copy 1 2 3 4 # Use extended config but override the port server: <<: *server_extended port: 8080 # Override just this one field Complete Multi-File Setup linkFile: config.yaml (Main config - minimal and clean!) YAML Copy 1 2 3 4 5 6 7 8 9 10 11 12 13 14 server: <<: *server_dev auth: <<: *auth_oidc integrations: <<: *integrations_full userDefaults: <<: *user_regular frontend: <<: *frontend_multi_theme To deploy to production: Change the anchor references: YAML Copy 1 2 3 4 5 6 7 8 9 10 11 12 13 14 server: <<: *server_production # Changed from *server_dev auth: <<: *auth_oidc integrations: <<: *integrations_no_office # Changed from *integrations_full userDefaults: <<: *user_readonly # Changed from *user_regular frontend: <<: *frontend_single_theme # Changed from *frontend_multi_theme Benefits link One-line switching - Change entire configuration profiles instantly Modularity - Each concern lives in its own file Reusability - Create multiple presets and reuse across environments Maintainability - Update one anchor to affect all configs using it Clean main config - Main config stays simple and readable Testing - Quickly test different configurations without code duplication Validation linkAll configurations must match the structure defined in your schema. The anchor system just provides a way to organize and reuse configuration blocks. Next Steps link Server configuration Authentication setup Environment variables

Frontend Customization