Table of Contents
- Introduction
- Installation

  | · Introduction · Windows installation · UNIX installation · Starting the Server · Directory Structure

- Handling Challenger
- Virtual Servers
- Configuration Examples
- Modules
- Filesystems
- RXML Tags
- Graphics
- Proxy
- Databases
- Miscellaneous Modules
- Security Considerations
- Scripting
- Frontpage
- Upgrading
- Third Party Extensions
- Portability
- Reporting Bugs
- Appendix

Introduction
Challenger is written in the Pike programming language and requires Pike to run, so when you install Challenger, Pike will also be installed. By default, Pike will be installed inside Challenger's directory structure. If you want to use Pike for other tasks as well you can install it elsewhere.

Challenger contains its own fairly complex directory structure. It is helpful for administrators to be acquainted with this structure, which is essentially the same as the one stored in the distribution package.

Challenger is started by the shell script `server/start`. For an automatic restart of Challenger when the system is rebooted, this script should be called during the boot procedure of the operating system.

Challenger consists of two processes, the start script and a Pike process. The start script will be running to ensure a restart of Challenger in case the Pike process is killed or the user chooses to restart Challenger.