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
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. However, FastCGI scripts that are in $HOME/public_html/cgi-bin/ will be executed as plain CGI scripts, even if they have the .fcgi extension.

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</tt>) can be used anywhere in your public_html</tt>.

For information about CGI and Perl, see the Perl page.

Logs

 * Access and error logs are located in /var/log/http/</tt> on the web servers.
 * PHP (and CGI?) logs are located in /var/log/userlog/</tt> on the web servers.

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

Frequently asked questions

 * Where can I find documentation about my programming language?
 * For generic questions, try Google or an IRC channel. Some specific issues have been documented on this wiki at the programming language's name, e.g., Perl.


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


 * How does URL rewriting and authentication work?
 * See ZWS.


 * Is there a license requirement for my tools?
 * See Default license.