On Mon, Aug 15, 2011 at 10:16:29AM -0400, Ben Timby wrote: > In the above way, the administrator could delegate control of portions > of the configuration to a user without the overhead of an .htaccess > file. Also, you could include a file which in turn includes other > files. Thus, the administrator could delegate via httpd.conf a config > file to the user which in turn could delegate to a set of files. This > would give you localized management in a set of files. There are two problems with this which I can see. Firstly, from the web server manager's point of view this is a bad idea, because all it would take would be for the user to construct a conf file with a syntax error and the whole server is taken down. Too much of a risk on a shared server. Secondly, from the user's point of view, they make their change to the conf file, but it will only become active when the server is restarted to pick up the changes, so probably daily or worse weekly. With a .htaccess file the changes are instantaneous. So, while it's nice in theory, there are practicalities which mean that it is unlikely to happen in a shared server scenario. > I think the way things are today is good and not in need of > improvement in the way you suggest. Most of what you want can be > accomplished using the above method, now to convince your server > administrator. I think an experienced server admin would shoot this one down pretty quickly. Pete -- Openstrike - improving business through open source http://www.openstrike.co.uk/ or call 01722 770036 / 07092 020107
Attachment:
pgpKaDSI5DVO3.pgp
Description: PGP signature
|