Setting up a custom TADS Web server

If you have your own Web server machine, and you have some expertise at setting up Apache Web servers and related software, you can contribute computing power to the TADS "cloud" by setting up a TADS Web server on your machine. This chapter explains how.

Note that you don't need to set up a TADS server if all you want to do is deploy your TADS Web UI game. There's an existing public cloud of servers for any player running any game. To deploy your game, you merely have to upload it to the IF Archive and create an IFDB page for it. The Web deployment chapter has the details.

The TADS Web Play system is designed to work as a flexible "cloud" utility service where any number of servers can be added to the network. Each player is dispatched at game startup to an available server, so that the CPU load is distributed throughout the network. Servers are only called upon to contribute CPU power to the network - they don't have to worry about storing any long-term data, because the games (.t3 files) are downloaded dynamically at start-up, and saved files are stored on IFDB. This means that each server only has to install a generic set of software (namely, the TADS interpreter and a basic Apache/php/MySQL suite); servers don't have to worry about hosting games or user files. Running a TADS server doesn't require a lot of disk space.

If you prefer, you can use SQLite instead of MySQL as the database engine. SQLite is smaller in terms of memory footprint and CPU load, so it might be preferable if you're using a low-cost VPS, where memory and CPU time are rationed.

If you don't already run your own Web server, but you're still interested in contributing to the TADS server cloud, look into getting a VPS (Virtual Private Server) from a commercial Web hosting service. Lots of hosting companies offer VPS plans, and they can be quite cheap if you shop around - as of this writing, it's easy to find one for under $10 a month with enough horsepower for TADS Web serving.


TADS Interpreter: You'll obviously need a TADS interpreter that has the full networking functionality, so your server will have to run a supported operating system, such as Windows or Linux.

Root/administrator access: You'll generally need full administrator (root) access to your machine, since you'll have to configure the regular Web server on the machine (e.g., Apache) and install the TADS interpreter software. (This usually rules out "shared hosting" plans with Web hosts. A VPS or dedicated server is recommended.)

Static, public network address: In order to act as a server on the public Internet, your machine must have a network address that's static (that is, permanently assigned to your machine) and public (visible on the Internet, not just on a local subnet). This can be a static numeric IP address, or a registered domain name.

If your machine is on a home network with a broadband router, it probably uses a private subnet address, such as a 192.168.x.x address; and if you have home broadband service through a phone or cable company, you probably have a dynamic public IP address for your router that changes from time to time. It's possible to work around both of these conditions; there are services that let you assign a DNS name to a dynamic IP address, for example, and some broadband routers have advanced configuration settings for exposing servers. The details are beyond the scope of this chapter, so you'll need the relevant expertise if you want to attempt this type of configuration.

(L)AMP: The TADS server package is based on the popular free software stack known as "LAMP" - Linux, Apache, MySQL (or SQLite), php. TADS runs on Linux as well as other operating systems, so the actual required stack is just the "AMP" part. The instructions below assume you're using an Apache server with php and MySQL or SQLite installed, but leave the choice of operating system up to you.

Step-by-step instructions

Install the TADS Interpreter

The first step is to install a TADS interpreter. For Linux, install FrobTADS. Build and install exactly as you would for local play.

Install Apache, MySQL/SQLite, and php

Some Linux distros come with the LAMP components pre-installed, so you might not need to install anything manually. If your Linux doesn't include LAMP out of the box, you should be able to use your system's package manager to install them from the command shell. The command syntax varies by Linux variety, so you'll have to consult your system's manuals for specific instructions.

For more information about the specific components, here's where to go:

Configure Apache

Follow the instructions in your Apache distribution to set up the basic Web server. The t3launch scripts don't have any special configuration requirements for Apache and should work with a typical default installation.

Here are the key things to check in your Apache configuration file (usually called httpd.conf or apache2.conf):

Install the t3launch scripts

Download the package from Install as follows:

Configure your database

The t3launch scripts need a database engine to manage a local "cache" of .t3 files downloaded from other servers. The .t3 files that your server runs will generally be hosted on another server, such as the IF Archive ( When a player starts a game, your server has to transfer the .t3 file from the hosting site to your server's local disk, via an HTTP GET, so that the TADS interpreter can load it. If the file has been transfered previously, though, t3launch simply re-uses the existing local copy; it uses a MySQL table to keep track of this.

You can use either MySQL or SQLite as the database engine.

MySQL: Set up a t3launch database and user account on your MySQL database. You can do this by entering the following commands using the mysql command-line tool:

You can substitute different values for the user name, password, and database name. Use the names you choose here for the DB_USERNAME, DB_PASSWORD, and DB_SCHEMA parameters in the configuration file setup below.

SQLite: SQLite uses a binary file to store its database tables. You'll have to choose a directory where this file will be stored. The directory must be readable and writable by the Web server process, which typically runs as user "nobody".

The following commands (entered at the Unix command line) will configure the directory permissions and create an empty file for the database. Log in as root (or use "su root") to run these commands.

You can substitute a different directory and/or database file name of your choosing. Use the file name and location you choose here for the DB_FILE parameter in the configuration file setup below.

Configure the t3launch scripts

The t3launch scripts need to be customized for your machine's specific configuration. The configuration variables are in the file t3launch/inc/config.php within your Apache Document Root directory. Edit this file, and adjust the following variables as needed:

Tweak your Linux configuration

This step is optional. If you're running a Linux server, and you have root access, you can improve TADS server performance by adding the following line to the file /etc/sysctl.conf:

echo "0" > /proc/sys/net/ipv4/tcp_slow_start_after_idle

You'll need root privileges to edit that file, so use "su root", or log in as root to start with. Changes to /etc/sysctl.conf don't take effect until you reboot the server, but you can put this change into effect immediately simply by running the command above as a shell command; again, you'll need root privileges. If you're running on a shared server and you don't have root access, you can skip this step, since it's only a performance optimization.

Test your configuration

First, check that your launch script starts up properly, by opening a Web browser and typing this in the address bar:


Replace address with your server's numeric IP address (or, if your server has a DNS name, you can use the domain name). If it's working correctly, you'll see a simple text page saying "OK". If that's not what appears, something's wrong with your configuration.

Next, check that your Apache server is correctly denying Web access to the supporting scripts in the "inc" directory, by trying this URL in your browser:


Again, use your actual IP or domain in place of address. The result should be a "403 - Forbidden" error. If you don't get the 403 error, something's wrong. This is important for your site's security, because the "inc" scripts contain private configuration information, such as your MySQL password. If you see php source code when you request that address, make sure that your Apache configuration file allows .htaccess overrides in the "inc" folder.

Register your server with IFDB

To participate in the IFDB switchboard system (which dispatches players to your server) and the IFDB storage server (which provides centralized "cloud" storage for saved games), you must register your server with IFDB. The process for this isn't currently formalized or automated, since we don't expect a huge number of servers. Simply send email to the IFDB administrators (see the IFDB contact information) with the following:

IFDB will assign your server a server ID and storage API key. You'll need this information in the next step.

Note that your storage API key is essentially a password, authenticating your server to the storage server for file transactions. You should keep this private; for example, be careful not to store it in a file that's accessible via your Apache server. The API key is a security measure to limit access to the storage server to recognized game servers, to help protect user files against unauthorized access.

Create a tadsweb.config file

Create a file called tadsweb.config in the directory containing your TADS interpreter program file. This is a simple text file; edit it with Notepad, emacs, vi, or any other text editor of your choice. Enter the following information, one variable per line:

The server ID and storage API key are the values you receive when you register your server with IFDB. If you're setting up a private server that's not meant to be part of the TADS cloud, you can omit the server ID and storage server entries.

The "watchdog" setting is described further below.

The watchdog

The interpreter has a self-monitoring feature called the watchdog. The watchdog looks for potential problems with the bytecode program's behavior, and terminates the program if it appears to be misbehaving. You can turn this setting on or off in your tadsweb.config file. Currently, the watchdog is implemented only on Unix and Linux platforms; the configuration setting is ignored on other systems.

The watchdog looks for these conditions:

If you plan to include your server in the TADS cloud, or you're otherwise going to allow people to run arbitrary third-party .t3 programs, you should enable the watchdog. The watchdog is designed to minimize your server administration work by automatically detecting and killing buggy programs that you'd otherwise have to kill manually, such as programs stuck in infinite loops and programs that don't know when to quit.

If you're setting up a server to run just your own TADS programs, and you're not allowing third-party programs, you might or might not want to enable the watchdog. The watchdog is less important when you're running a known set of programs, since you can test the programs you're hosting to make sure they don't have any of the bugs that the watchdog would catch. Of course, bugs can be fiendishly clever at slipping through testing, so you might still want the watchdog as a backup. On the other hand, you might specifically not want the watchdog if your programs intentionally do some of the things that the watchdog targets, such as heavy number-crunching or running without a client. Those are perfectly legitimate application behaviors; the watchdog only targets them because they're inappropriate for a shared, public server. If you're hosting your own programs on your own private server, you're of course free to number-crunch with abandon, or to host a Web server (or other continuous network service) written with TADS. Turning off the watchdog will allow such applications to run without interference.

How the launch process works

For those interested, here are the details of how the different machines and components interact. You might find this helpful if you're trying to write a non-LAMP replacement for the launch page.

There are three separate machines involved in playing a server-based TADS game:

We're only concerned here with that last item, the TADS server. The client is just a PC (or phone, pad, etc) with a browser; IFDB is managed by its own administrators, so we don't have to worry about that.

On the TADS server machine, there are two main bits of software you have to install. The first is the TADS interpreter; the second is a conventional Web server, generally an Apache server with MySQL and php, as outlined above.

When a player decides to start a game session, they click on a link in their browser. That link might come from the game's IFDB page or from the game author's Web site; that's not really important, though, since all that matters is that they reach the "t3run" page on IFDB. This is the IFDB switchboard for the game. It looks through its list of available game servers - a list that will include your server, once you register it - and selects one to handle the new session. It then sends the client an HTTP redirect with the Internet address of the selected server. Let's assume that your server is the one selected.

The browser follows this redirect to your server. At this point, your server is just sitting there idling, awaiting new connections. The TADS interpreter isn't running at all yet. So how does the server even know about new connection requests? This is where your Apache Web server comes in. Apache's job is to continually monitor port 80 - the standard port for Web servers - waiting for someone to send in an HTTP request. When the player's browser follows the redirect instructions from IFDB to your machine, what it's really doing is sending an HTTP request to port 80 on your machine. Apache receives this request and handles it.

Apache's response to the HTTP request from the client is to execute a php program that's part of the TADS server package, called t3launch.php. This program creates a new TADS process on the server machine, passing parameters to the new process that tell it which game (.t3 file) to run. The interpreter loads the .t3 file. Assuming that the .t3 file is a Web UI game, the game will set up its own internal Web server. This server opens a new network listener port - not port 80, which is already taken by Apache, but simply an arbitrary port number that's not being used by someone else, as assigned by the operating system. TADS relays this information back to the t3launch program. t3launch in turn relays it back to the client browser, in the form of another HTTP redirect. This new redirect tells the browser how to connect to the game's internal Web server on its newly created port number.

The client browser follows the new redirect, which connects it to the game's internal Web server. The game takes it from here; the Apache server's job is done for now, and it simply goes back to monitoring port 80 for new connection requests.

Here's a diagram showing the various steps. Note that the TADS Interpreter process doesn't exist initially - it doesn't exist until step 4, where Apache launches it.