Changeset 1905

Show
Ignore:
Timestamp:
08/26/08 19:10:14 (3 months ago)
Author:
taher
Message:

--

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved

  • cherokee/trunk/doc/basics.txt

    r1816 r1905  
    77   - link:basics_installation_unix.html[Unix]: Installation on Unix/Linux platforms. 
    88   - link:basics_installation_windows.html[Windows]: Installation on Windows platform. 
     9   - link:basics_installation_svn.html[From SVN]: Installation of the development release. 
    910 . link:basics_upgrade.html[Upgrading Cherokee]: Upgrading from a previous release? 
    1011 . link:basics_running_cherokee.html[Running Cherokee]: Basic steps to run Cherokee. 

  • cherokee/trunk/doc/cookbook_django.txt

    r1816 r1905  
    3131---- 
    3232$ cd /var/www 
    33 $ django-admin.py startproject example 
     33$ django-admin startproject example 
    3434---- 
    3535 

  • cherokee/trunk/doc/modules_loggers_combined.txt

    r1816 r1905  
    2626The description of the aditional fields follows. 
    2727Refer to the link:modules_loggers_ncsa.html[Common Log 
    28 Format]documentation for information about the rest of the fields. 
     28Format] documentation for information about the rest of the fields. 
    2929 
    3030 

  • cherokee/trunk/doc/other_faq.txt

    r1901 r1905  
    4242---- 
    4343 
    44 === How to compile it on Windows 
    4544 
    46 ---- 
    47 ./configure --prefix=/usr --sysconfdir=/etc  \ 
    48   --localstatedir=/var --enable-trace        \ 
    49   --enable-static-module=all --enable-static \ 
    50   --enable-shared=no --enable-beta 
    51 ---- 
     45=== How to access cherokee-admin from a remote machine 
    5246 
    53 === How to cross compile the Win32 version 
    54  
    55 * From Linux: http://alobbs.com/news/1201 
    56 * From MacOS: http://alobbs.com/news/1299 
    57  
    58  
    59 === Accessing cherokee-admin from a remote machine does not work. Is it broken? 
    60  
    61 No it is not. cherokee-admin binds only to local loopback by 
    62 default. There are some workarounds: 
     47cherokee-admin binds only to local loopback by default. There are some 
     48workarounds: 
    6349 
    6450* Create an SSH tunnel. This is the recommended way. In order to do so 
    …… 
    8167  the device running the cherokee instance you wanted to set up. 
    8268 
    83 === I cannot run cherokee-admin. Is there a way to replicate its work by hand? 
     69=== How to manually write configuration files without cherokee-admin 
    8470 
    85 Yes there is. The configuration file is a plain text file and its 
    86 syntax is well documented. Check the 
    87 link:dev_cherokee.conf.html[cherokee.conf] internal format 
    88 information. Notice that it is not the recommended method, but the 
    89 format will always be kept updated to facilitate scripting tasks, 
    90 working with embedded devices and other similar situations. 
     71The configuration file is a plain text file and its syntax is well 
     72documented. Check the link:dev_cherokee.conf.html[cherokee.conf] 
     73internal format information. Notice that manually editing the 
     74configuration is not the recommended method, but the format will 
     75always be kept updated to facilitate scripting tasks, working with 
     76embedded devices and other similar situations. 
    9177 
    9278=== Does Cherokee speak WSGI natively like `mod_wsgi` does? 
    …… 
    9581`mod_wsgi` for a number of reasons. 
    9682 
    97 Firstly, from the architectural point of view we do not think it is 
    98 wise to embed into the web server a huge interpreter that is linked 
    99 against dozens of libraries. 
     83* First, and purely from an architectural point, embedding an 
     84interpreter into the web server doesn't feel quite right. Be it a huge 
     85interpreter linked against dozens of libraries or be it something 
     86using Python's shared libraries, it doesn't fit with the design 
     87principles applied throughout Cherokee's code base. 
    10088 
    101 Second, it sounds hard to believe that mod_wsgi is faster than a plain 
    102 and simple SCGI application writing to a Unix socket: WSGI applications 
    103 can also use link:modules_handlers_fcgi.html[FastCGI] and 
     89* Second, it sounds hard to believe that `mod_wsgi` is faster than a 
     90plain and simple SCGI application writing to a Unix socket: WSGI 
     91applications can also use link:modules_handlers_fcgi.html[FastCGI] and 
    10492link:modules_handlers_scgi.html[SCGI] backends, which are fully 
    105 supported by Cherokee. 
     93supported by Cherokee. At least running `mod_wsgi` in daemon 
     94mode. When run as an embedded part of the web server, as the author of 
     95`mod_wsgi` pointed out, there should be a performance gain because 
     96there is no socket involved nor any wire protocol related to 
     97marshalling of data across the socket. In this case the information is 
     98passed directly to the Python web application in the same process via 
     99the WSGI programmatic API. However by running this as an embedded 
     100component we feel that we would be violating the design principles 
     101mentioned above, and would affect security and reliability of the web 
     102server. 
    106103 
    107104We believe Cherokee should be as fast, light, clean and secure as