While I'm not sure I completely understand what you're suggesting, it
seems to me that unless we work with third-party re-packagers,
anything of this nature that we do is merely an academic exercise,
since only a rapidly-decreasing minority of users will ever even
experience it.
My other initial reaction is that it makes the configuration files
that much harder to find, and frustrate people a little more.
What are you thoughts on those issues?
On Jun 8, 2010, at 5:21 AM, Jorge Schrauwen wrote:
Note: This proposal is for trunk, not 2.3/2.4 or earlier.
I propose provide a recommendation for providing examples.
conf/examples/{protocol}/mod/{module_name}.con and conf/examples/
{protocol}/mod/{module_name}/*
Additional modules could also drop examples in the correct directory.
Maybe we could also replace the default httpd.conf with one telling
the user to pick one from conf/examples/http and adjust it to there
needs.
Ofcourse some good default configurations need to be provided in
that directory.
Example of a default configuration that will tell users to configure
httpd:
---
Listen 80
User apache
Group apache
LoadModule dir_module modules/mod_dir.so
LoadModule authz_host_module modules/mod_authz_host.so
<Directory />
Deny from all
Options None
AllowOverride None
</Directory>
ErrorDocument 403 "<!DOCTYPE html><html><head><title>Apache HTTPD
Server</title></head><body><h2>Apache HTTPD is working correctly</
h2>Please configure your server.</body></html>"
---
The above provide a secure default that will only display a message.
Kind Regards
Jorge Schrauwen
--
Rich Bowen
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
