Multiple Virtual Web Servers As an ISP you probably want to host multiple customer Web sites on a
single heitml Web server. In this respect heitml is fully integrated
into the Apache server configuration. You can use all the Customers can use .htaccess files located in the document directories to
set options themselves. In general customers can change only those options,
that are not set explicitly inside the global configuration ( Most important is the <VirtualHost demo.h-e-i.de> heitml on heitmlkey 0dJlNz-2DyOng-3zPPN2-0yk3mJ # set the session directory heitmlSessionDir /usr/local/heitml/session/demo </VirtualHost>
The In addition you need various global entries in httpd.conf. If you installed heitml on the main server these entries should be present already. # The following lines are needed if the dynamic linked version # of heitml is used loadmodule heitml_module .../mod_heitml_PostgreSQL.so # Make the .hei extension known to Apache addtype application/x-heitml hei # disallow overriding of heitml options heitmloverride off # set limits heitmlTimeLimit 600 heitmlMemLimit 24000 heitmlMemExit 2000 DirectoryIndex index.htm index.html index.heiLoadModule is required if the dynamically linked (DSO) version of heitml is used. The addtype makes the .hei extension known to Apache. heitmloverride off is always needed for hosting and disallows options
in the .htaccess file to override global options. The heitmlTimeLimit makes sure
that heitmlMemLimit on the
other hand limits the memory used. If you do not use these limits, customers
can make your server overflow by using too much memory or computing
time. heitmlMemExit will terminate apache child processes when the use
more memory than specified (in kb). Using directory index you can specify what file is shown if the user
requests a subdirectory. Apache usually uses "index.html". For heitml it is
very useful to add "index.hei".
Next
|