John Plocher wrote: > Have you looked at how debian does this? > > IIRC, they have a whole dir structure that deals with sites, configs and > modules > that is managed with symlinks rather than editing config files...
One does not have to always edit the config file. Editing is needed only when the user wants to customize the settings. And, of course symlink, too, can be created, but not recommended because the files in samples-conf.d get overwritten during upgrade whereas the ones in conf.d are retained. > It might be worth looking at, even if the end result is an informed "no thanks"... > Yes, I did look at debian's structure. Theirs is more granular (e.g., .load file for every individual module) which leads to too many configuration files. Apache 2.2.6 and above is something in-between and not very different from what was supported earlier. If required, we can think of supporting such a configuration, in future, as it involves many more changes. Thanks, Seema. > > Jyri Virkki wrote: >> I am sponsoring this case for Seema Alevoor and closing it approved >> automatic. >> >> >> Template Version: @(#)sac_nextcase 1.64 07/13/07 SMI >> This information is Copyright 2008 Sun Microsystems >> 1. Introduction >> 1.1. Project/Component Working Name: >> Apache 2.2 config samples directory structure >> 1.2. Name of Document Author/Supplier: >> Author: Seema Alevoor >> 1.3 Date of This Document: >> 28 February, 2008 >> 4. Technical Description >> >> Apache 2.2 config samples directory structure >> >> Background: >> >> PSARC/2007/586 "Including Apache 2.2.6 with Solaris" approved the >> integration of Apache 2.2.6 into Nevada with the following >> configuration directory structure (later PSARC/2008/118 updated Apache >> to 2.2.8): >> >> /etc/apache2/[version] >> /conf.d/ >> /original/ >> /original/extra/ >> >> As a recap, the contents under /etc/apache2/[version]/original/extra >> directory were delivered as-is from the Apache distribution and these >> files are never read by the server. They are there as examples only. >> >> This location has proven confusing and users find it hard to find the >> example configuration files. Furthermore, since these files were >> delivered as-is, not all of them necessarily even work in OpenSolaris. >> This led to even more confusion when users attempted to copy them >> into the config directory and found that didn't work. >> >> To improve the user experience, this project creates a new directory, >> "samples-conf.d", under /etc/apache2/[version] directory. It will >> contain the sample configuration files with any and all necessary >> OpenSolaris-specific modifications. This will enable the user to use >> them by simply copying them to conf.d directory. >> >> This project removes the redundant >> /etc/apache2/[version]/original/extra/ directory. >> >> >> Exported Interfaces >> ------------------- >> /etc/apache2/2.2/samples-conf.d Uncommitted >> >> >> 6. Resources and Schedule >> 6.4. Steering Committee requested information >> 6.4.1. Consolidation C-team Name: >> sfw >> 6.5. ARC review type: Automatic >> 6.6. ARC Exposure: open >> >> _______________________________________________ >> opensolaris-arc mailing list >> opensolaris-arc at opensolaris.org > > _______________________________________________ > > > webstack-discuss mailing list > webstack-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/webstack-discuss
