Changeset 1765
- Timestamp:
- 08/07/08 16:25:18 (4 months ago)
- Files:
-
- cherokee/trunk/doc/Makefile.am (modified) (4 diffs)
- cherokee/trunk/doc/TOC.txt (modified) (5 diffs)
- cherokee/trunk/doc/TODO (modified) (2 diffs)
- cherokee/trunk/doc/basics.txt (added)
- cherokee/trunk/doc/basics_installation.txt (added)
- cherokee/trunk/doc/basics_installation_windows.txt (modified) (6 diffs)
- cherokee/trunk/doc/basics_upgrade.txt (modified) (1 diff)
- cherokee/trunk/doc/build/chunked_template.conf (modified) (1 diff)
- cherokee/trunk/doc/bundle.txt (added)
- cherokee/trunk/doc/bundle_cget.txt (modified) (1 diff)
- cherokee/trunk/doc/bundle_cherokee-admin.txt (modified) (6 diffs)
- cherokee/trunk/doc/bundle_cherokee-config.txt (modified) (1 diff)
- cherokee/trunk/doc/bundle_cherokee-guardian.txt (modified) (2 diffs)
- cherokee/trunk/doc/bundle_cherokee-tweak.txt (modified) (2 diffs)
- cherokee/trunk/doc/bundle_cherokee.txt (modified) (1 diff)
- cherokee/trunk/doc/config.txt (added)
- cherokee/trunk/doc/config_encoding.txt (modified) (1 diff)
- cherokee/trunk/doc/config_quickstart.txt (modified) (3 diffs)
- cherokee/trunk/doc/config_virtual_servers.txt (modified) (4 diffs)
- cherokee/trunk/doc/config_virtual_servers_rule.txt (modified) (2 diffs)
- cherokee/trunk/doc/cookbook.txt (added)
- cherokee/trunk/doc/dev.txt (added)
- cherokee/trunk/doc/media/css/cherokee_doc.css (modified) (2 diffs)
- cherokee/trunk/doc/modules.txt (added)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
cherokee/trunk/doc/Makefile.am
r1755 r1765 15 15 doc_DATA = \ 16 16 TOC.inc \ 17 basics.html \ 17 18 basics_why_cherokee.html \ 18 19 basics_requirements.html \ 19 20 basics_download.html \ 21 basics_installation.html \ 20 22 basics_installation_unix.html \ 21 23 basics_installation_windows.html \ 22 24 basics_upgrade.html \ 23 25 basics_running_cherokee.html \ 26 bundle.html \ 24 27 bundle_cherokee.html \ 25 28 bundle_cherokee-admin.html \ … … 29 32 bundle_spawn-fcgi.html \ 30 33 bundle_cget.html \ 34 config.html \ 31 35 config_quickstart.html \ 32 36 config_general.html \ … … 37 41 config_mime_types.html \ 38 42 config_advanced.html \ 43 cookbook.html \ 39 44 cookbook_cross_compilation.html \ 40 45 cookbook_authentication.html \ 41 46 cookbook_ssl.html \ 47 modules.html \ 42 48 modules_balancers_round_robin.html \ 43 49 modules_encoders_gzip.html \ … … 60 66 modules_validators_pam.html \ 61 67 modules_validators_plain.html \ 68 dev.html \ 62 69 dev_debug.html \ 63 70 dev_cherokee.conf.html cherokee/trunk/doc/TOC.txt
r1757 r1765 1 ************************** 2 Getting started 3 ************************** 1 ********************************* 2 link:basics.html[Getting started] 3 ********************************* 4 4 5 . link:basics_why_cherokee.html[Why Cherokee?] 5 6 . link:basics_requirements.html[Requirements] 6 7 . link:basics_download.html[Download] 7 . link:basics_installation_unix.html[Installation: Unix] 8 . link:basics_installation_windows.html[Installation: Windows] 8 . link:basics_installation.html[Installation] 9 - link:basics_installation_unix.html[Unix] 10 - link:basics_installation_windows.html[Windows] 9 11 . link:basics_upgrade.html[Upgrading Cherokee] 10 12 . link:basics_running_cherokee.html[Running Cherokee] 11 13 12 ************************** 13 Cherokee Bundle 14 ************************** 14 ********************************* 15 link:bundle.html[Cherokee Bundle] 16 ********************************* 17 15 18 . link:bundle_cherokee.html[cherokee] 16 19 . link:bundle_cherokee-admin.html[cherokee-admin] … … 20 23 . link:bundle_cget.html[cget] 21 24 22 ************************** 23 Configuration 24 ************************** 25 ********************************* 26 link:config.html[Configuration] 27 ********************************* 28 25 29 . link:config_quickstart.html[Quickstart] 26 30 . link:config_general.html[General] … … 32 36 . link:config_advanced.html[Advanced] 33 37 34 ************************** 35 Cookbook 36 ************************** 38 ********************************* 39 link:cookbook.html[Cookbook] 40 ********************************* 41 42 //// 37 43 Reference table <8> link:cookbook_reference.html[] 38 44 Optimizing Cherokee <2> link:cookbook_optimizing_cherokee.html[] 39 Cross compilation [12] link:cookbook_cross_compilation.html[]45 . link:cookbook_cross_compilation.html[Cross compilation] 40 46 Embedding Cherokee <9> link:cookbook_embedding_cherokee.html[] 41 47 Managing logs <5> link:cookbook_managing_logs.html[] <rotations and cherokee-tweak?> … … 45 51 Setting up Django <4> link:cookbook_django.html[] 46 52 Setting up RoR <4> link:cookbook_ror.html[] 53 //// 47 54 48 ************************** 55 ********************************* 49 56 Modules 50 ************************** 57 ********************************* 58 59 //// 51 60 Balancers link:modules_balancers.html[] 52 61 Round robin [24] link:modules_balancers_round_robin.html[] … … 76 85 pam [7.4] link:modules_validators_pam.html[] 77 86 plain [7.5] link:modules_validators_plain.html[] 87 //// 78 88 79 ************************** 89 ********************************* 80 90 Other resources 81 ************************** 91 ********************************* 92 82 93 FAQ 83 94 Community 84 95 85 ************************** 96 ********************************* 86 97 Development info 87 ************************** 98 ********************************* 99 88 100 . link:dev_debug.html[Debugging] 89 101 . link:dev_cherokee.conf.html[cherokee.conf] 90 API introduction link:dev_api.html[] 91 Examples link:dev_examples.html[] 102 //// 103 . API introduction link:dev_api.html[] 104 . Examples link:dev_examples.html[] 105 //// cherokee/trunk/doc/TODO
r1752 r1765 8 8 Currently the structure reflects more the internal architecture of 9 9 Cherokee rather than a traditional manual. 10 *[3] Integrate the current docs into the new tree.11 *[4] Define and document a series of typical configuration tasks.10 [3] Integrate the current docs into the new tree. 11 [4] Define and document a series of typical configuration tasks. 12 12 13 13 Tasks to be documented: 14 14 ------------------------------------- 15 *<1> How to configure virtual hosts from beginning to end, step by step.15 <1> How to configure virtual hosts from beginning to end, step by step. 16 16 * <2> How to tune scalability (IO cache & file, number of threads, increment 17 17 descriptors...) … … 20 20 * <5> How to manage logs (make specific mention of usage of Cherokee-Tweak). 21 21 * <6> How to manage security (SSL/TLS, certs, etc) 22 * <7> Development documentation would be nice to have, Stefan de Konink 23 suggested example handlers *fully* documented and documenting the API, 24 though this last thing might be slightly out of the normal user 25 documentations scope. A Development section could be introduced when we 26 design the new general draft. 22 * <7> Development documentation 27 23 * <8> Reference table of functionalities to be achieved (and hopefully 28 24 a full setup example). cherokee/trunk/doc/basics_installation_windows.txt
r1720 r1765 41 41 software mentioned in the following lines. 42 42 43 *MinGW*: minimalist GNU for Windows (GCC & binutils)43 .*MinGW*: minimalist GNU for Windows (GCC & binutils) 44 44 45 45 * Download MinGW release 5.1.4 at the time of this writing. … … 49 49 50 50 51 *MSYS*: Minimal SYStem51 .*MSYS*: Minimal SYStem 52 52 53 53 * Download MSYS, tests were made with release 1.0.10 … … 56 56 * Answer y, y, c:/MinGW 57 57 * You should add something like this to your ~/.profile to process 58 your preferences: 59 58 your preferences: 59 + 60 60 ------------------------------ 61 61 if [ -f ${HOME}/.bashrc ] then … … 64 64 ------------------------------ 65 65 66 *MSYS DTK*: Dev Toolkit66 .*MSYS DTK*: Dev Toolkit 67 67 68 68 * Get DTK 69 69 * Install it in the same path as above 70 70 71 *Update Autoconf & Automake*71 .*Update Autoconf & Automake* 72 72 73 73 * You might encounter problems if you do not have up to date … … 75 75 versions 2.61 and 1.10.1, that are the ones we used. 76 76 77 *Pthreads Win32*: POSIX Threads77 .*Pthreads Win32*: POSIX Threads 78 78 79 79 * Cherokee will need these. Just download … … 82 82 83 83 84 *Python*84 .*Python* 85 85 86 86 * You will need this, since both the build process and cherokee/trunk/doc/basics_upgrade.txt
r1724 r1765 15 15 scripts: 16 16 17 ---- 17 18 contrib/07to08.py /path/cherokee.conf.07 /path/cherokee.conf.08 19 ---- 18 20 19 21 If you need to upgrade from a really old release, simply apply the cherokee/trunk/doc/build/chunked_template.conf
r1757 r1765 19 19 <body> 20 20 <div id="wrapper"> 21 <div id=" content">21 <div id="page_content"> 22 22 23 23 [footer] 24 24 </div> 25 25 </div> 26 <div id=" nav">26 <div id="page_nav"> 27 27 include::../TOC.inc[] 28 28 </div> cherokee/trunk/doc/bundle_cget.txt
r1752 r1765 24 24 explicitly. Below is a summary of the cget options. 25 25 26 Startup: 27 ~~~~~~~~ 28 -V, --version ::26 - *Startup* 27 28 -V, --version;; 29 29 Display version of currently installed cget and exit. 30 30 31 -h, --help ::31 -h, --help;; 32 32 Display help screen with common options. 33 33 34 Logging and input file: 35 ~~~~~~~~~~~~~~~~~~~~~~~ 34 - *Logging and input file* 36 35 37 -q, --quiet ::36 -q, --quiet;; 38 37 Run in quiet mode: no output is displayed. 39 38 40 Download: 41 ~~~~~~~~~ 39 - *Download* 42 40 43 -O, --output-document=FILE ::41 -O, --output-document=FILE;; 44 42 Writes whatever document is downloaded to FILE 45 43 46 HTTP options: 47 ~~~~~~~~~~~~~ 44 - *HTTP options* 48 45 49 -s, --save-headers ::46 -s, --save-headers;; 50 47 This option saves HTTP headers to the file being saved (speciâ 51 48 fied with -O option) 52 49 53 --header=STRING ::50 --header=STRING;; 54 51 this option inserts STRING among the headers sent in the HTTP 55 52 request. cherokee/trunk/doc/bundle_cherokee-admin.txt
r1740 r1765 9 9 image::media/images/admin_index.png[Cherokee Admin interface] 10 10 11 If you want to access the administration interface from the same computer that you installed cherokee on 12 simply start the administration interface by running: 11 If you want to access the administration interface from the same 12 computer that you installed cherokee on simply start the 13 administration interface by running: 14 13 15 14 16 ---- … … 16 18 ---- 17 19 18 Then redirect your web browser to 127.0.0.1:9090 this is the default port for the19 administration interface. 20 Then redirect your web browser to 127.0.0.1:9090 this is the default 21 port for the administration interface. 20 22 21 23 image::media/images/admin_launch.png[Cherokee admin interface] 22 24 23 If you want to access the administration interface from another computer, you need to bind the cherokee 24 administration interface to all network interfaces: 25 If you want to access the administration interface from another 26 computer, you need to bind the cherokee administration interface to 27 all network interfaces: 28 25 29 26 30 ---- … … 28 32 ---- 29 33 30 WARNING: By starting cherokee-admin listening on all interfaces, everyone that can access the computer can31 alter your cherokee configuration. Don't use this in a production environment! 32 It is much better to use 'ssh -L' in these cases. These are the 33 necessary steps to be taken to create an SSH tunnel. This is the 34 recommended way. In order to do so you must issue the following 35 command: 34 WARNING: By starting cherokee-admin listening on all interfaces, 35 everyone that can access the computer can alter your cherokee 36 configuration. Don't use this in a production environment! It is much 37 better to use 'ssh -L' in these cases. These are the necessary steps 38 to be taken to create an SSH tunnel. This is the recommended way. In 39 order to do so you must issue the following command: 36 40 37 41 ---- … … 47 51 48 52 .Example: 49 Make cherokee use a different configuration file, listen on port 9091 and grab 50 the administration interface application from a different path: 53 Make cherokee use a different configuration file, listen on port 9091 54 and grab the administration interface application from a different 55 path: 56 51 57 ---- 52 58 cherokee-admin -a -P 9091 -C /etc/cherokee/cherokee2.conf \ … … 70 76 `cherokee-admin` accepts the following options: 71 77 72 -h, --help ::78 -h, --help;; 73 79 Shows brief usage information 74 80 75 -V, --version ::81 -V, --version;; 76 82 Show version and exit 77 83 78 -b, --bind[=IP] ::84 -b, --bind[=IP];; 79 85 By default `cherokee-admin` binds only to 127.0.0.1 (localhost), 80 86 which means you can only connect to it from the same system. … … 84 90 85 91 86 -C, --target=PATH ::92 -C, --target=PATH;; 87 93 Requests a configuration file different than the default 88 94 /etc/cherokee/cherokee.conf to be used 89 95 90 -d, --appdir=DIR ::96 -d, --appdir=DIR;; 91 97 Uses a custom admin-interface path 92 98 93 -p, --port=NUM ::99 -p, --port=NUM;; 94 100 Specifies an alternative port. By default, 9090. 95 101 cherokee/trunk/doc/bundle_cherokee-config.txt
r1740 r1765 26 26 `cherokee-config` accepts the following options: 27 27 28 --version ::28 --version;; 29 29 Print the currently installed version of CHEROKEE on the standard output. 30 30 31 31 32 --libs ::32 --libs;; 33 33 Print the linker flags that are necessary to link a CHEROKEE program. 34 34 35 --cflags ::35 --cflags;; 36 36 Print the compiler flags that are necessary to compile a CHEROKEE program. 37 37 38 38 39 --prefix=PREFIX ::39 --prefix=PREFIX;; 40 40 If specified, use PREFIX instead of the installation 41 41 prefix that CHEROKEE was built with when computing the cherokee/trunk/doc/bundle_cherokee-guardian.txt
r1724 r1765 6 6 added besides the syntax of the command. The main usage of this 7 7 utility is determining the used flags during the compilation and 8 linking process. This is useful to build programs that make use of Cherokee. 8 linking process. This is useful to build programs that make use of 9 Cherokee. 10 9 11 10 12 This is the full information provided by the manpage. … … 17 19 18 20 *DESCRIPTION*:: 19 cherokee is an extremely fast, flexible and embeddable web server. 20 cherokee-guardian is the recommended way to invoke cherokee - It will 21 launch Cherokee with any options specified to it via the command line, 22 and monitor it. In case Cherokee ends abnormally, it will be immediâ 23 ately re-launched.24 25 In future versions, cherokee-guardian will probably become the main 26 binary to invoke Cherokee.21 Cherokee is an extremely fast, flexible and embeddable 22 web server. cherokee-guardian is the recommended way to invoke 23 cherokee. It will launch Cherokee with any options specified 24 to it via the command line, and monitor it. In case Cherokee 25 ends abnormally, it will be immediately re-launched. 26 + 27 In future versions, cherokee-guardian will probably become the 28 main binary to invoke Cherokee. 27 29 ********************************************************************** 28 30 cherokee/trunk/doc/bundle_cherokee-tweak.txt
r1740 r1765 36 36 cherokee-tweak accepts the following options: 37 37 38 -h, --help ::38 -h, --help;; 39 39 Shows brief usage information 40 40 41 -V, --version ::41 -V, --version;; 42 42 Prints version and exits 43 43 44 -u, --user= STRING ::44 -u, --user= STRING;; 45 45 Specifies the user name with which to identify to the server 46 46 47 -p, --password=STRING ::47 -p, --password=STRING;; 48 48 Specifies the password with which to identify to the server 49 49 50 -c, --command=STRING ::50 -c, --command=STRING;; 51 51 Required option. Command to execute: logrotate, trace or info 52 52 53 -a, --url=URL ::53 -a, --url=URL;; 54 54 Required option. URL where the administrative interface can be 55 55 found. This target must be defined previously in cherokee- … … 59 59 highly encouraged. 60 60 61 -l, --log=PATH ::61 -l, --log=PATH;; 62 62 Log file to be rotated (Only to be used when -c is logrotate) 63 63 64 -t, --trace=STRING ::64 -t, --trace=STRING;; 65 65 Modules to be traced (Only to be used when -c is trace). Cheroâ 66 66 kee must have been compiled with the --enable-trace for this to cherokee/trunk/doc/bundle_cherokee.txt
r1740 r1765 22 22 This command will launch the Cherokee webserver. It accepts the following options. 23 23 24 -h, --help ::24 -h, --help;; 25 25 Prints a brief help message and terminates execution 26 26 27 -V, --version ::27 -V, --version;; 28 28 Prints Cherokeeâs version and terminates execution 29 29 30 -t, --test ::30 -t, --test;; 31 31 Perform a sanity check on the configuration file. The server will not run. 32 32 33 -d, --detach ::33 -d, --detach;; 34 34 Launches the server as a background process (default behaviour is to stay attached to the controlling terminal). 35 35 36 -C, --config=PATH ::36 -C, --config=PATH;; 37 37 Specifies a configuration file other than the default /etc/cherokee/cherokee.conf 38 38 39 -p, --port=PORT ::39 -p, --port=PORT;; 40 40 TCP port number to which the server will listen. 41 41 42 -r, --documentroot=PATH ::42 -r, --documentroot=PATH;; 43 43 Launches a server exposing statically the specified directory. When launched with -r, the configuration file is ignored, and the Cherokee instance runs with its default values. 44 44 45 -i, --print ::45 -i, --print;; 46 46 Print server technical information. 47 47 ********************************************************************** cherokee/trunk/doc/config_encoding.txt
r1740 r1765 13 13 Whenever you set up a virtual server, 14 14 link:modules_encoders_gzip.html[gzip] is enabled by default for the 15 following file types: html, htm, txt, css & js15 following file types: `html`, `htm`, `txt`, `css` and `js`. 16 16 17 17 You are encouraged to use this. Hardware is cheap. Bandwidth is not. cherokee/trunk/doc/config_quickstart.txt
r1755 r1765 131 131 know, in the Internet), you will need proper DNS records. 132 132 133 `default` 134 ^^^^^^^^^ 133 *`default`*:: 135 134 We will leave default untouched except for the document root path, 136 135 which we will change. This is done through the `Basics` tab. 137 136 You could create by hand '/var/www/default' for example and set it up 138 137 in the appropriate field. 139 138 + 140 139 If you access your machine by IP or a DNS resolution points in that 141 140 direction for any particular domain, the contents of your document 142 141 root directory will be exposed ('/var/www' by default unless you 143 142 changed that during the build process). 144 143 + 145 144 Right now any file with the 'php' extension will be served after being 146 145 processed by the PHP interpreter (you should have `php-cgi` installed 147 146 in your system for this, though). 148 147 + 149 148 Any requested file would be sent. If a directory is requested, a file 150 149 called index.php or index.html will be served if it is present (the … … 155 154 `List & Send` handler for the `Static Content` handler. 156 155 157 `example` 158 ^^^^^^^^^ 156 157 158 *`example`*:: 159 159 For now this virtual server is an exact copy of the untouched 160 160 `default` virtual server. Create some new directories 161 '/var/wwww/example', '/var/wwww/example/auth' and 162 '/var/www/example/redir', and configure the first one as default 163 document root path. 164 161 '/var/wwww/example' and '/var/wwww/example/auth', and configure the 162 first one as default document root path. 163 + 165 164 Next, setup `example.net` and `example.com` in the `Domain names` tab. 166 165 We'll erase everything in the *Targets* list within the `Behavior` 167 166 tab, except the `default` rule. With this we'll only be able to serve 168 167 static content. 169 168 + 170 169 Accessing the URL http://example.org should now show a list of 171 170 available files and directories under '/var/www/example/'. 172 171 + 173 172 Now lets password protect the `auth` directory. Add a new `Directory` 174 173 class rule pointing to `/auth`. Then, through the `Security` tab, add 175 174 a `Validation Mechanism` under `Authentication`. 176 175 + 177 176 The field `Realm` is mandatory. Lets set it as `Secured Area`. 178 177 If you choose `PAM` and impose no more restrictions, only users with … … 184 183 For example, it could have been `/var/www/passwords.txt` with the 185 184 following contents: 186 185 + 187 186 ---- 188 187 testuser1:password1 189 188 testuser2:password2 190 189 ---- 191 190 + 192 191 Note that the rule must not be flagged as `Final`, or else no other 193 192 rules will be applied afterwards and no access will be given to any 194 193 contents. This is because at this point we have not defined any 195 194 handler for the `/auth` rule and nothing would be served. 196 195 + 197 196 Refer to the Cookbook for detailed examples on the different options. 198 197 + 199 198 Lastly, lets configure a redirection rule by choosing a "Regular 200 199 Expression" as the new rule type. Type the following regex: `^/rss.*$` 201 200 Then, within the `Handler` selection tab specify a target: `/feed` 202 201 + 203 202 image::media/images/admin_rule_regex.png[Regex] 204 203 + 205 204 And voilà ! A request of the form http://example.net/rss2 would be 206 205 redirected to http://example.net/feed 207 206 + 207 Note that the `Type` of the *Redirection* is `External`. This means 208 the server will instruct the requesting web client to fetch the 209 redirected URL, which means the client will allways know what the 210 final URL is. This also means the redirection can be done to servers 211 other than your own. If it were internal, the redirection would be 212 invisible (no URL rewrite), but if it was done to an external server 213 the `Virtual Domain` setting wouldn't apply and your `default` virtual 214 domain would have to handle the connection. Having the theoretical 215 content hosted elsewhere, an error would occur. 216 + 208 217 A much more general redirection could be one using these values: 209 210 * *Regular Expression*::218 + 219 *Regular Expression*;; 211 220 `^/(.*)$` 212 213 * *Substitution*:: 214 http://www.cherokee-project.com/example/$1 215 216 This would redirect every petition to a mirror hosted elsewhere. 221 + 222 *Substitution*;; 223 http://www.example.com/example.net/$1 224 225 + 226 Note that this rule would have to be external since `example.com` is 227 not among the domains managed by our configuration. 228 + 229 This would redirect every petition to a site hosted under 230 `http://example.com/example.net`. For instance, the request for 231 `http://example.net/image.jpg` would return 232 `http://example.com/example.net/image.jpg`. cherokee/trunk/doc/config_virtual_servers.txt
r1744 r1765 112 112 113 113 It can accepted either FQDN (Fully Qualified Domain Names) or wild 114 card entries. For instance: 115 114 card entries. 115 116 For instance:: 117 + 116 118 ---- 117 119 example.com … … 199 201 ********************************************************************** 200 202 - link:modules_handlers_common.html[common] - **List & Send** 201 203 + 202 204 Combines both `Static Content` and `Only listing` handlers 203 205 functionality to behave similarly to common web servers, it will … … 206 208 207 209 - link:modules_handlers_file.html[Static Content] - **Static Content** 208 210 + 209 211 This is the file handler and it serves files straight from the 210 212 file system. 211 213 212 214 - link:modules_handlers_dirlist.html[dirlist] - **Only listing**: 213 215 + 214 216 Displays a directory content list when a directory is requested, 215 217 but it does not allow to download any content. 216 218 217 219 - link:modules_handlers_redir.html[redir] - **Redirection** 218 220 + 219 221 Perform simple and/or complex redirections using regexes. 220 222 221 223 - link:modules_handlers_cgi.html[cgi] - **CGI Execution** 222 224 + 223 225 Executes CGI programs. 224 226 225 227 - link:modules_handlers_fcgi.html[fcgi] - **FastCGI Server Support** 226 228 + 227 229 Communicates with FastCGI servers. 228 230 229 231 - link:modules_handlers_scgi.html[scgi] - **SCGI Server Support** 230 232 + 231 233 Communicates with SCGI servers. 232 234 233 235 - link:modules_handlers_server_info.html[Server Info] - **Server 234 236 Info** 235 237 + 236 238 Provide some configurable information about the server. 237 239 238 240 - link:modules_handlers_mirror.html[Generic balancer] - **Generic 239 241 balancer** 240 242 + 241 243 Select one of the available mechanisms to distribute the load (locally 242 244 or remotely). … … 244 246 - link:modules_handlers_admin.html[Remote Administration] - **Remote 245 247 Administration** 246 248 + 247 249 Implements an administration interface to work with 248 250 link:bundle_cherokee-tweak.html[cherokee-tweak]. cherokee/trunk/doc/config_virtual_servers_rule.txt
r1752 r1765 41 41 ^^^^^^^^ 42 42 43 Allow access only from the IPv6 localhost address: 44 43 - Allow access only from the IPv6 localhost address 44 + 45 45 ---- 46 46 Allow from ::1 47 47 ---- 48 48 49 Allow access from the 127.0.0.0/8 network: 50 49 - Allow access from the 127.0.0.0/8 network 50 + 51 51 ---- 52 52 Allow from 127.0.0.0/8 53 53 ---- 54 54 55 or it could also we written like: 56 55 - or it could also we written like 56 + 57 57 ---- 58 58 Allow from 127.0.0.0/255.0.0.0 59 59 ---- 60 60 61 It is also possible to use lists instead of a single IP or network61 - It is also possible to use lists instead of a single IP or network 62 62 range. And there is even the possibility of mixing IPv4 and IPv6 63 addresses and networks if you want ::64 63 addresses and networks if you want 64 + 65 65 ---- 66 66 Allow from 192.168.0.0/16, ::1, 10.0.0.1, 3ffe:3200::/24 … … 76 76 validaton mechanism. The following `validators` are available: 77 77 78 - link:modules_validators_plain.html[plain] - **Plain text file** 78 - link:modules_validators_plain.html[plain] - **Plain text file** 79 + 80 Uses a plain flat file to perform HTTP authentication. 79 81 80 Uses a plain flat file to perform HTTP authentication. 82 - link:modules_validators_htpasswd.html[htpasswd] - **Htpasswd file** 83 + 84 Uses an htpasswd file to perform HTTP authentication. 81 85 82 - link:modules_validators_htpasswd.html[htpasswd] - **Htpasswd file** 86 - link:modules_validators_htdigest.html[htdigest] - **Htdigest file** 87 + 88 Uses an htdigest-generated file to perform HTTP authentication. 83 89 84 Uses an htpasswd file to perform HTTP authentication. 90 - link:modules_validators_ldap.html[ldap] - **LDAP server** 91 + 92 Uses an LDAP directory to perform HTTP authentication. 85 93 86 - link:modules_validators_htdigest.html[htdigest] - **Htdigest file** 94 - link:modules_validators_mysql.html[mysql] - **MySQL server** 95 + 96 Uses a MySQL database to perform HTTP authentication. 87 97 88 Uses an htdigest-generated file to perform HTTP authentication. 89 90 - link:modules_validators_ldap.html[ldap] - **LDAP server** 91 92 Uses an LDAP directory to perform HTTP authentication. 93 94 - link:modules_validators_mysql.html[mysql] - **MySQL server** 95 96 Uses a MySQL database to perform HTTP authentication. 97 98 - link:modules_validators_pam.html[PAM] - **PAM Authentication** 99 100 Uses PAM to perform HTTP authentication. 98 - link:modules_validators_pam.html[PAM] - **PAM Authentication** 99 + 100 Uses PAM to perform HTTP authentication. 101 101 102 102 cherokee/trunk/doc/media/css/cherokee_doc.css
r1758 r1765 180 180 // margin-right: 10%; 181 181 // margin-top: 1.5em; 182 // margin-bottom: 1.5em; 183 } 182 margin-bottom: 1.5em; 183 } 184 184 185 div.admonitionblock { 185 186 margin-top: 2.5em; … … 361 362 margin-right: -200px; 362 363 } 363 # content {364 #page_content { 364 365 margin-right: 210px; 365 366 } 366 # nav {367 #page_nav { 367 368 font-size: 0.8em; 368 369 width:200px;