vertigo-apache

Features

PHP support uses the suphp apache module when PHP support is enabled, this is done to ensure that the PHP scripts is run as the unix user of a particular domain, rather than the user running the apache server.

Directories

• apache The directory where the apache configuration files should be generated, one for each domain. Ususally this is /etc/vertigo/apache
• htpasswd Many services require some form of authentication, for instance vertigo-stats, and this directory specifies where vertigo-apache should generate the required htpasswd files. Usually this is /etc/vertigo/htpasswd
• templates Directory containing all the templates that vertigo-apache uses, they all have a name starting with apache.
• www The directory where the users web-files is located, if you want suexec to work (and if you want CGI support you do) this directory should be below the suexec root as set when apache was compiled. On Debian this is /var/www
• certificates (optional) This points to the directory containing the SSL certificates to use for SSL support.

Files

• apache-all (optional) Some older versions of apache did not support using the Include directive on a directory, and required it to be a file. If this file is set (usually to /etc/vertigo/apache/all.conf) a file with an Include directive for each domain is generated.

Variables

• webmaster The email address for the system administrator(s) of this web-server.

Regarding SSL support

Besides not being very securely shared (see Vertigo/Services/Certificate) if certificates are missing apache refuses to serve pages! So be sure that the server generating certificates runs vertigo-update before the web servers tries to use the certificates after running vertigo-update.

Another thing is that SSL doesn't really support name-based virtual hosting, because SSL (Secure Socket Layer) actually is designed to be protocol agnostic the SSL layer doesn't know the name of the server the user is connecting to, only the ip-address of the server. This means that eventhough we generate (and specify) different certificates for each served domain and its subdomains, we end up just serving the first certificate specified, work is being done on fixing this by smart people. And rest assured that as soon as this is fixed vertigo will support it as soon as possible.

For now we will just have to live with users complaining about the "warnings" presented by thier browsers.