Deploying | [Configuration] | [Customizing]
<h1>Deploying Toadhttpd</h1>

Toadhttpd distributes with a tcl based build tool that can perform local installations or shrink wrap all of the critical pieces into a self-contained executable. Toadhttpd prefers to maintain its own copies of modules, rather than rely on packages managed by teapot or the local operating system. This means that two independent copies of toadhttpd can be resident on the same server at the same time.
<p>
These instructions will become more elaborate as we move out of the design phase and into the <i>this is production software!</i> phase.
<p>
For now the instructions to set up toadhttpd are to unpack the fossil repository into a folder. (Not the folder you are going to install to!). And then use the make.tcl script to have toadhttpd assemble everything it will need.
<p>
Toadhttpd depends on the following external projects:

<h2>tcllib</h2>
Official: <a
Mirror: <a
<p>
Tcl Standard Library. NOTE: You will need to check out the <i></i> branch. It has the most up-to-date implementation of the httpd module.

<h2>Taolib</h2>
Official: <a
<p>
The Tcl Architecture of objects. Basically, a big reusable framework for TclOO code.

<h2>Toadhttpd</h2>
Official: <a
<p>
This project
<hr>

When I got to set things up, here are the steps:

<verbatim>
mkdir -p
fossil clone
fossil clone
fossil clone
mkdir -p
cd
fossil open
mkdir -p
cd
fossil open trunk
mkdir -p
cd
fossil open trunk

tclsh make.tcl install
</verbatim >

This will install all of the code needed to run toadhttpd in the directory Change that to whatever suits for your needs.

To run toadhttpd:

<verbatim>
cd
tclsh httpd.tcl
</verbatim>

The stock server will serve up content from the <b>htdocs</b> directory inside of wherever toadhttpd was installed.

For more on customizing your installation see [Configuration].