[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: docs updated, working copy of php draft now available online



On Fri, August 5, 2005 05:11, sean finney wrote:
>>         3.2.1: Config files generated via a web interface should exist
>>             in /etc, inasmuch as they can still be edited by hand
>
> this is something we'll need to have a more thorough discussion about.
> typically, when config files are overwritten by programs they should go
> in /var/lib and then be referenced via config files in /etc.

Well, any sensible web application that writes config files will first
read in the previous values. E.g.: I edit the settings by hand, and then
access the online configuration system of the webapp, then I will be
presented with the values as I've set them by hand, right?

If some do not, I would split this into two categories: if the automated
writing the config file is just a configuration frontend that takes
current config into account, it could be just under /etc. If the webapp
writes something out 'blindly', i.e. local modifications will be lost,
then it should be under /var.



Thijs



Reply to: