Project Info | Installation Guide | Object Diagram

Steps:
1. MySQL | 2. InkTank Web | 3. Archangel

Now for the hardest part…

Before we start on the InkTank Web installation, make sure you have the important information written down from the last section:

• Your MySQL server's hostname—the “database address.”
• The name of your database. (suggested: inktanksql)
• Your admin username and password. suggested: (ikadmin)
• Your web username and password. (suggested: ikweb)

Create a subdomain to use for InkTank.

InkTank uses friendly, permanent URLs. It is suggested that you create a permanent subdomain to use with your new archives, however, InkTank itself can be installed wherever you like. Creating subdomains is, however, beyond the scope of this InkTank install document. Your webhosting provider will have extensive documentation on the subject. For DreamHost, the instructions are in the Knowledge Base.

Create a location to store the InkTank files, peferably by creating a blank subdomain.

Download and configure InkTank.

From the project files page, grab the latest InkTank version. If you're using Windows, it's the .zip version you want. Extract it somewhere on your hard drive. Inside, you'll find the raw .php files that make InkTank run. We're interested in the files within the distribution directory.

You will need to copy config-dist.txt into the InkTank directory — in other words, move it out of the distribution directory. Then open it in your favorite text editor: NotePad, TextEdit, or vi will work nicely.

Within the config file are instructions. You will need to modify the file using the information you gathered in the last section. Follow the directions in the file. When you're done, rename the file to “config.php.”

Upload InkTank to your server.

Using FTP, upload the contents of the InkTank data from the .zip file (not the directory itself, nor the zip file) to your favorite storage location on your server. Your webhost is guaranteed to have great directions for doing this, but I bet you know how to already.

Note that you must upload the file .htaccess from the zipfile. Don't forget it. You'll find your site works except you can't browse authors, view stories, or see awards if you forget it.

Remove installation.php.

When you access your new InkTank installation, if all went well, you should see a notice that you need to remove installation.php. Delete it. Otherwise, follow its instructions to (hopefully) diagnose any installation problems you may have had.

Try it out!

Congratulations, if everything went well, your InkTank installation is ready to be accessed by the world. (Don't forget about that delay your webhost might have, though.) Go to your subdomain, and revel in your newly created InkTank installation. Of course, you can't add or change anything yet—but that's the next step. Continue on…

Troubleshooting.

InkTank didn't work perfectly on the first attempt? Too bad… Here's a list of common mistakes and problems you might have encountered. If you've tried them all and still have problems, post a message in our forthcoming online dicussion forums.

1. If you see errors about connecting to the database, that nasty delay may still be in effect, or you may have mistyped your username or password in the config.php file. Double-check your work.
2. If you receive a 404 error when you click on a story name, your web-provider may not support manual .htaccess files. Rename the files "archive," "awards," and "pairings," putting .php on the ends of their filenames. Edit config.php and change ASM('Archive Script Extension',''); to ASM('Archive Script Extension','php');. Your URLs will be uglier, but installation should work.
3. If you're still getting 404's, you may be on a Microsoft IIS webserver, which does not permit URLs in the style InkTank uses ,with a basic IIS configuration. Sorry to spoil the party, but InkTank won't work. You could e-mail your webhost and ask if they expect forthcoming support for resolving URLs that are beneath PHP files, like "award.php/Pulitzer_Prize.html."