1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
|
<html>
<head>
<title>Cherokee 0.7 Documentation</title>
<link href="media/css/documentation.css" type="text/css" rel="stylesheet" />
</head>
<body>
<h1>Cherokee 0.7 Documentation</h1>
<p>Welcome to the 0.7 documentation.</p>
<div class="section" id="compiling-and-installing">
<h1>Compiling and Installing</h1>
<p>If you are not comfortable with rolling your own Cherokee, then check our
listings of pre-compiled <a class="reference external" href="http://www.cherokee-project.com/downloads">binaries</a>.
Specific instructions for building your own copy are available at:</p>
<ul class="simple">
<li><a class="reference external" href="compiling_and_installing_unix.html">Unix</a></li>
<li><a class="reference external" href="compiling_and_installing_windows.html">Windows</a></li>
</ul>
</div>
<div class="section" id="configuration-interface">
<h1>Configuration Interface</h1>
<p>Cherokee provides an administration interface named <a class="reference external" href="admin.html">Cherokee Admin</a>
that allows to configure the web server without having to worry about
editing a text file written with a certain syntax.</p>
<div align="center" class="align-center"><img alt="Cherokee Admin interface" class="align-center" src="media/images/admin_index.png" /></div>
</div>
<div class="section" id="general-configuration">
<h1>General configuration</h1>
<p>There are a number a <a class="reference external" href="general.html">general configuration</a> entries that specify the
most significant configuration options such as the port - or ports -
that the server will listen to, the default timeout, whether to
support keep-alive connections and so on.</p>
</div>
<div class="section" id="virtual-servers">
<h1>Virtual Servers</h1>
<p>If you want your web server to work with more than one <a class="reference external" href="vserver.html">virtual
server</a> you will have just to create them. Each more will have a
complete independent configuration: paths, behavior, logging
facilities, etc.</p>
</div>
<div class="section" id="encoders">
<h1>Encoders</h1>
<p>The encoders allow to transform whatever information the server
is sending as a response of a request, no matter what handler
is generating it.</p>
<ul>
<li><p class="first"><a class="reference external" href="encoders/gzip.html">gzip</a> - GZip compression</p>
<p>Encodes the output with GZip</p>
</li>
</ul>
</div>
<div class="section" id="icons">
<h1>Icons</h1>
<p>The <a class="reference external" href="icons.html">icons</a> configuration associates an icon image with one or more file
extensions. This information will be used mainly by the <a class="reference external" href="handlers/dirlist.html">dirlist</a> handler.</p>
</div>
<div class="section" id="advanced-topics">
<h1>Advanced topics</h1>
<p>There is an <a class="reference external" href="advanced.html">advanced section</a> that allows to configure the most
complex parameters of the server and how it works with the operating
system.</p>
<p>If you are unsure about any of the options presented within the
advanced section, we recommend you to not change it and use the
default value.</p>
<div class="section" id="other-advanced-topics">
<h2>Other advanced topics</h2>
<ul class="simple">
<li><a class="reference external" href="debug.html">Debugging</a> Cherokee</li>
<li>How to <a class="reference external" href="cross_compile_cherokee.html">cross compile Cherokee</a> (Win32 from Linux or OS X)</li>
<li>How to <a class="reference external" href="How_to_generate_SSL_keys.html">generate SSL keys</a></li>
</ul>
</div>
<div class="section" id="internal-configuration-system">
<h2>Internal configuration system</h2>
<p>The administration interface is highly recommended, and is in fact the
only administration mechanism that should be used to configure
Cherokee. However, there is another way in which Cherokee developers
and very advance users can modify the configuration.</p>
<p>The <a class="reference external" href="internal_configuration.html">internal configuration system</a> text file format is documented so
if you are completely sure about what you are doing, you can modify it
by hand. We recommend you not to do so.</p>
<p>The default location for Cherokee configuration files is
<tt class="docutils literal"><span class="pre">/etc/cherokee</span></tt>, but this may vary based on distribution or
installation parameters.</p>
</div>
</div>
</body>
</html>
|
