• Why Cherokee?Feature overview.
• RequirementsHardware and software requirements.
• DownloadWhere and how to download Cherokee.
• InstallationInstallation instructions.
• Upgrading CherokeeUpgrading from a previous release?
• Running CherokeeBasic steps to run Cherokee.

• WalkthroughOverview and walkthrough.
• HomeMain section.
• StatusServer status information.
• GeneralGeneral settings.
• Virtual serversServer definition.
• Information SourcesDefining information sources.
• AdvancedAdvanced tweaking. Not for the faint of heart.
• WizardsConfiguration assistants for many known scenarios.

• AuthenticationHow to set up authenticated resources.
• Cross compilationHow to cross compile Cherokee.
• DBSlayerHow to set up DBSlayer MySQL balancing.
• Embedding CherokeeCherokee on embedded devices.
• MaintenanceSeamlessly switching to maintenance mode.
• Managing logsSeamless log rotation.
• Optimizing CherokeeRecommendations and tweaks.
• RedirectionsCommon redirection examples.
• SSL/TLS, certsSecure connection tips.
• HTTPS acceleratorSSL Offloading with Cherokee.
• StreamingHow to stream Audio and Video with Cherokee.
• PHPHow to run PHP apps with Cherokee.
• Ruby on RailsHow to run Ruby on Rails apps with Cherokee.
• DjangoHow to run Django apps with Cherokee.
• ColdFusionHow to run ColdFusion apps with Cherokee.
• DrupalHow to run Drupal on Cherokee.
• WordpressHow to run Wordpress on Cherokee.
• AlfrescoHow to run Alfresco on Cherokee.
• ASP.NETHow to run ASP.NET apps with Mono and Cherokee.
• GlassFishHow to run Java apps with Cherokee.
• JoomlaHow to run Joomla on Cherokee.
• KumbiaHow to run Kumbia apps with Cherokee.
• LiferayHow to run Liferay on Cherokee.
• MailmanHow to run Mailman on Cherokee.
• MoodleHow to run Moodle on Cherokee.
• NagiosHow to run Nagios with Cheroke.
• phpBBHow to run phpBB on Cherokee.
• phpMyAdminHow to run phpMyAdmin on Cherokee.
• SugarCRMHow to run SugarCRM on Cherokee.
• Concrete5How to run Concrete5 on Cherokee.
• SymfonyHow to run Symfony apps with Cherokee.
• TracHow to run Trac on Cherokee.
• ZendHow to run Zend apps with Cherokee.
• uWSGISetting up Cherokee for uWSGI.
• HTTP to HTTPSHow to redirect all traffic from HTTP to HTTPS.
• Restricting traffic by IPHow to restrict traffic based on incoming IP.
• Domain matchingMatching domains and subdomains with Cherokee.

• HandlersConnection handling modules.
• ValidatorsAuthentication mechanisms.
• EncodersCompression and filtering.
• LoggersLogging mechanisms.
• BalancersLoad balancing strategies.

• FAQList of Frequently Asked Questions.
• Front-line CacheSpecifics of the Caching subsystem.
• System TuningTweaking the OS for maximum performance.
• Cherokee GoodiesInteresting Cherokee features.
• Usage graphsInformation on the several graphs available.
• SignalsSignals supported by Cherokee.
• CommunityMore information sources.
• Common errorsSome typical production errors and their cause.
• Man pagesDetails about each program bundled with Cherokee.

• QuickstartWhere to start?
• DebuggingResources available to debug Cherokee.
• cherokee.confInternal configuration specs.
• Quality AssuranceSome info about QA in Cherokee.
• CTKDive into the Cherokee Toolkit.

• Introduction to DevelopmentHow to build a package.

Configuration

Index → Configuration

General Configuration

Network

Network settings

IPv6 support

The IPv6 configuration key brings the possibility of activating or deactivating the IPv6 support at the server. If Cherokee has been compiled with IPv6 support (--with-ipv6), this configuration entry will be fully functional, otherwise it will be ignored.

SSL/TLS Back-end

Specifies the TLS/SSL backend to be used, if any. The current option is OpenSSL.

Timeout

Sets the number of seconds that Cherokee will wait before closing the connection.

Server Tokens

This specifies the string that Cherokee should use to identify itself.

Parameters	Description
Product	Cherokee
Minor	Cherokee/0.98
Minimal	Cherokee/0.98.3
OS	Cherokee/0.98.3 (UNIX)
Full	Cherokee/0.98.3 b2955 (UNIX)

By default, Cherokee will use Full.

Graphs type

Through this you can enable or disable the usage of RRD graphs. Check the usage graphs section for more details.

Ports to listen

Ports

This section allows to configure the ports that the server will be listening to. You can add several different ports, and configure whether they will be used for HTTP or HTTPS.

Each binding entry can be configured to listen to a network interface. In case the text entry is empty, the server will accept connections from that port on any interface.

Server Permissions

Permissions

User & Group

The User directive configures which user the Cherokee daemon will normally run as. By default, Cherokee runs as root which is considered undesirable in all but the most trustful network configurations.

The User directive used in conjunction with the Group directive instructs the daemon to switch to the specified user and group as quickly as possible after startup.

There are two possible formats: using the user or group name, or using the system ID.

Chroot

Cherokee can be jailed inside a directory. Note that this should not be used as the sole security measure.

Icon management

The icons configuration file associates an icon image with one or more file extensions. This information will be used mainly by the dirlist handler.

• Extensions

  • This allows to associate icons with extensions.

• Files

  • This section lets you specify an icon for certain filenames such as "core" or "README". It accepts wild-card strings (using * and ?)

• Special icons

  • Directory: In this case, it specifies the icon to be used with Directories.

  • ParentDirectory: This entry is used to assign an Icon to the "go to the parent directory" action.

  • Default: This is the icon that will be shown if any of the previous ones matched.

Icons

MIME Types

This section allows to add support for new MIME types or edit the existing ones.

• Mime Type: this is the proper mime string.

• Extensions: the file extensions for this type of contents.

• Max Age: defines for how long a file of this type must be cached at the client’s side.

MIME Types