Toolserver:Web hosting

The Toolserver provides web hosting to users. Your files should be placed in $HOME/public_html/, and they will be accessible from the Internet at  http:// toolserver.org/~ /.

Note: For tools, we recommend using multi-maintainer projects. This allows one tool to have multiple maintainers and a stable URL, rather than being tied to a single user. However, you can also put tools under your own account if you like.

CGI & PHP
For CGI scripts, there are two options: plain CGI and FastCGI. If possible, you should use FastCGI, since it's faster, and reduces the load on the web server. However, if you have already-written CGI scripts, you can use them unmodified if you don't have the time to convert them to FastCGI.

To use FastCGI scripts, place them in $HOME/public_html/, with the extension .fcgi, and make sure they're executable.

To use plain CGI scripts, place them in $HOME/public_html/cgi-bin/. They do not need a particular file extension (like .cgi), but they do have to be executable.

PHP scripts (which must have the extension .php) can be used anywhere in your public_html.

FastCGI for PERL
The following code shows how to create PERL scripts that use FastCGI. Note that although CGI::Fast is installed on the web server, it may not be installed on the login servers. It is available from CPAN.

Logs
Access and error logs are located in /var/log/http/</tt> on wolfsbane</tt> and stable</tt>

Webalizer statistics for toolserver.org are here (updated every 6 hours). Contact Duesentrieb if this is broken.

FAQ

 * Why do I get an error 500 if I try to run my Perl CGI script?
 * Use the short checklist or the long checklist to find the answer.


 * Is it possible to use .htaccess</tt>-files?
 * Yes.


 * I need the perl module FOO::Bar. How do I install it?
 * Just fill in a bugreport at JIRA. Otherwise, if there is some good reason to install it locally, use the following instructions: Installing perl modules into your $HOME


 * How does url-rewriting and authentication work?
 * See ZWS.