For whatever it's worth, I think I agree with sol. If you look at common practices when installing web servers, it seems to be that the system is setup to point to a working instance.
The way I've used the default apache2 config scripts is to have one directory per enabled site underneath /var/www. So, for instance, if I wanted to have distinct secure and non-secure web spaces, I would have: /var/www/apache2-secure be the directory where the HTML, PHP, et al was stored for the secure server. /etc/apache2/sites-available/secure be the configuration file for the secure server, and /etc/apache2/sites-enabled/secure be a link to ../../sites-available/apache2-secure to activate the server (or I would remove the link to deactivate the server.) Then I would replicate this configuration by having the files /var/www/nonsecure, /etc/apache2/sites-available/nonsecure and /etc/apache2/sites-enabled/nonsecure. I believe that pointing the default to /var/www does not provide adequate guidance for novice administrators and home users. -- Default config DocumentRoot points to /var/www/. https://bugs.launchpad.net/bugs/69387 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
