Changeset 1804
- Timestamp:
- 08/13/08 21:23:56 (3 months ago)
- Files:
-
- cherokee/trunk/doc/cookbook_authentication.txt (modified) (1 diff)
- cherokee/trunk/doc/cookbook_optimizations.txt (modified) (1 diff)
- cherokee/trunk/doc/modules.txt (modified) (1 diff)
- cherokee/trunk/doc/modules_validators_plain.txt (modified) (1 diff)
- cherokee/trunk/doc/other_goodies.txt (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
cherokee/trunk/doc/cookbook_authentication.txt
r1801 r1804 34 34 35 35 36 The details to set up the `htdigest` and `htpasswd` are exactly the 37 same as for `plain` validation. The only difference is the tools used 38 to create the passwords' file. 39 40 41 .htdigest 42 43 To use this handler you will need a file created by the `htdigest` 44 command. It is a tool to manage user files for digest (and basic) 45 authentication. 46 47 **** 48 Syntax:: 49 htdigest [ -c ] passwdfile realm username 50 51 The only optional parameter is `-c`, used to create the passwdfile or 52 overwrite it if it is present. 53 **** 54 55 To create a file for a `testuser` with `testpassword` you would have 56 to issue: 57 58 ----- 59 $ htdigest -c passwords.digest secret testuser 60 Adding password for testuser in realm secret. 61 New password: 62 Re-type new password: 63 64 $ cat pass 65 testuser:secret:f24f76261bcd65780b33edde00855897 66 ----- 67 68 .htpasswd 69 70 For this handle, the tool `htpasswd` is needed to create the 71 files. The basic usage information is this: 72 73 ***** 74 Usage:: 75 htpasswd [-cmdpsD] passwordfile username 76 + 77 htpasswd -b[cmdpsD] passwordfile username password 78 + 79 htpasswd -n[mdps] username 80 + 81 htpasswd -nb[mdps] username password 82 ***** 83 84 Refer to its documentation for details about the parameters. For our example, this 85 will suffice: 86 87 ---- 88 $ htpasswd -c /var/www/.htpasswd testuser 89 New password: 90 Re-type new password: 91 Adding password for user testuser 92 93 $ cat /var/www/.htpasswd 94 testuser:iqLGh2g/7bX7M 95 ----- 96 97 Remember that it is never recommended to place the file with the 98 passwords in a location fetchable from the webserver. This is true for 99 plain validation, htdigest, htpasswd and whatever file based system 100 you cross paths with. 101 102 36 103 //// 37 104 To be written 38 39 Details for htdigest, htpasswd, mysql and ldap. 105 Details for mysql and ldap, with screenshots. 40 106 //// cherokee/trunk/doc/cookbook_optimizations.txt
r1801 r1804 94 94 Advanced:: 95 95 + 96 * System tweaking: 97 - Threads: The default value is chosen so that it is more than enough 98 to saturate the processors. You will probably not get much out of 99 this setting, since a higher value will not produce better results 100 and a lower one will simply increase the amount of unused processor 101 power. 96 * *Threads*: The default value is chosen so that it is more than enough 97 to saturate the processors. You will probably not get much out of 98 this setting, since a higher value will not produce better results 99 and a lower one will simply increase the amount of unused processor 100 power. 102 101 + 103 - File descriptors: By deffinition, the higher this limit is, the104 less efficient will your system be in relative terms. However, it105 is understood that if you are tweaking this value is because you106 need to, that is, you have a very high load site. In these cases107 increasing the file descriptors' limit makes sense because the108 higher this limit is, the more connections Cherokee will be able to109 handle. By default Cherokee does not touch this value and it uses110 the one specified by your system.102 * *File descriptors*: By deffinition, the higher this limit is, the 103 less efficient will your system be in relative terms. However, it 104 is understood that if you are tweaking this value is because you 105 need to, that is, you have a very high load site. In these cases 106 increasing the file descriptors' limit makes sense because the 107 higher this limit is, the more connections Cherokee will be able to 108 handle. By default Cherokee does not touch this value and it uses 109 the one specified by your system. cherokee/trunk/doc/modules.txt
r1801 r1804 1 1 2 . link:modules_balancers.html[Balancers] 2 3 - link:modules_balancers_round_robin.html[Round robin] cherokee/trunk/doc/modules_validators_plain.txt
r1801 r1804 34 34 **** 35 35 testuser:testpassword 36 36 37 cherokee:webserver 37 38 **** cherokee/trunk/doc/other_goodies.txt
r1801 r1804 2 2 ---------------- 3 3 4 There are several important but mostly unknown features of Cherokee 5 that really do make a difference in real-world production environments. 4 There are several important features of Cherokee that really do make a 5 difference in real-world production environments. 6 7 [[cherokee-admin]] 8 Cherokee-Admin 9 ~~~~~~~~~~~~~~ 10 Cherokee bundles a one of a kind UI to set up every available feature 11 without the need of editing any configuration files by hand. It is a 12 modern and easy to manage application that allows to set up the server 13 with speed and ease. The interface is thoroughly documented trhoughout 14 Cherokee's documentation. 15 16 [[cherokee-tweak]] 17 Cherokee-Tweak 18 ~~~~~~~~~~~~~~ 19 The swiss-army knife of the Cherokee bundle. This little tool enables 20 you, among other things, to rotate the logs with absolutely no 21 downtime at all. No connections are lost. No delay happens. It can 22 also be used to trace Cherokee's state on the fly, even remotely and 23 on production servers. 24 25 This tool has its own documentation under the 26 link:bundle_cherokee-tweak.html[cherokee-tweak] section. 6 27 7 28 [[x-sendifle]]