Implement a interface-like system #3
Labels
enhancement
New feature or request
help wanted
Extra attention is needed
question
Further information is requested
Some options are commonly shared between different services. For example:
These options should be available for all services, but they should be implemented differently, each service has different config files. The next step may be making a system where the environmental substitution of configuration files is delegated to a common implementation, so that one can rely on original config files being in
/run/<service-name>/orig
and the modified version being in/run/<service-name>/subst
.Another example may be "user-group" handling, almost all services have a
user
andgroup
options. The semantics of these options are not well defined, while I personally try to adhere to some semantics, it would be best if this was formalized in an implementation external to individual modules.The text was updated successfully, but these errors were encountered: