Hello. A lot of packages do default configuration in /etc/project.conf and admin related stuff in /etc/project.d/whatsoever.conf to separate the distribution part from local overrides.
Every now and then it might be useful to switch changes on and off. The Debian apache2 package uses sites-available/ and sites-enabled/ folders. This is convenient. I use this idea as a blueprint for administration. I put local configuration stuff into /etc/project.available/ folders and symlinks into /etc/project.d/ folders. This allows to toggle on/off mode easily and is a coherent scheme (besides the little deviation in apache2). Is it reasonable to use this idea as "best practice" and implement it into Debian style administration recommendations? It works very well e.g. for repository usage /etc/apt/sources.list.available/ where an admin can look what is possible even if not part of the live system yet. This would allow to ship a bunch of suggestions without enabling them by default and without the need to edit the project.conf file. Please share your thoughts with the community. Was anything like this discussed previously? -- kind regards Frank
pgpINqh6vdMEj.pgp
Description: OpenPGP digital signature
