Enable Usage of Multiple Configuration Files

[0x0D15]

Prerequisites

• I have checked the Wiki and Discussions and found no answer

• I have searched other issues and found no duplicates

• I want to request a feature or enhancement and not ask a question

The problem

Currently AdGuardHome supports only a single designated configuration file, however across multiple deployments it is often useful to have a specific set of core configuration along with a series of deployment specific configurations with the ability to easily update the core configuration without touching the deployment specific config.

Proposed solution

The ability to define multiple configuration files of varying precedence would solve this problem as then any given configuration file can be updated completely independent of any others.

Alternatives considered and additional information

No response

[tjharman]

I think it's important to remember this application is aimed at home users - it's not expected you'd be mass deploying it I don't think.

[0x0D15]

Agreed, however personally I run 2-3 instances of AdGuardHome and even then its very useful to have distinct configuration files for different purposes. In general this is supported across much of UNIX via the drop in file method i.e. the .d config directory.

[kuvaldini]

you can run a bunch of services with different configs/workdirs, systemd (if you use it) allows service templates where parameter (e.g. path to config) can be passed to service-name@parameter.service and being taken inside service file with %i.

EXAMPLE systemctl cat beesd@

Description=Bees (%i)
Documentation=https://github.com/Zygo/bees
After=sysinit.target

[Service]
Type=simple
ExecStart=/usr/sbin/beesd --no-timestamps %i
CPUAccounting=true
CPUSchedulingPolicy=batch
....