./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var make
Here is a list of the most frequently asked questions. Please refer to the appropriate section of the documentation for more details.
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var make
It’s the default way.
./configure --prefix=/usr --sysconfdir=/etc \ --localstatedir=/var \ --enable-static-module=xyz
./configure --prefix=/usr --sysconfdir=/etc \ --localstatedir=/var \ --enable-static-module=all
openssl req -days 1000 -new -x509 -nodes \ -out /etc/cherokee/ssl/cherokee.pem \ -keyout /etc/cherokee/ssl/cherokee.pem
cherokee-admin binds only to local loopback by default. There are some workarounds:
Create an SSH tunnel. This is the recommended way. In order to do so you must issue the following command:
ssh -L 9090:localhost:9090 remote_IP
After that you can access the remote interface through http://localhost:9090 and every request will be forwarded to the remote IP running cherokee-admin.
Launch cherokee-admin with the -b parameter in order to force it to listen to all the network interfaces.
Finally you could always install cherokee on your local host, configure it there and then copy the generated cherokee.conf file to the device running the cherokee instance you wanted to set up.
The configuration file is a plain text file and its syntax is well documented. Check the cherokee.conf internal format information. Notice that manually editing the configuration is not the recommended method, but the format will always be kept updated to facilitate scripting tasks, working with embedded devices and other similar situations.
In short: not like mod_wsgi at all. There is native support for the uWSGI server, which is a fast (pure C), self-healing, developer-friendly WSGI server aimed for professional python webapps deployment and development. Cherokee also provides a wizard to adjust its settings to those defined in the uWSGI configuration file of your project.
The list is documented in the Signals entry.
Check the Cookbook, there is a recipe on the subject.
Cherokee is licensed under the GNU General Public License, version 2, which can be found in the file COPYING distributed with the source code. For more details, read the full license in the project’s SVN repository.
If for whatever reason this license does not suit your needs, other licensing schemes can be negotiated on a particular basis. Contact Octality if this is your case.
The documentation is distributed under a Creative Commons Attribution (by) license, which is the most accommodating in terms of what others can do with it. It lets others distribute, remix, tweak, and build upon the work, even commercially.
The documentation is written and maintained using AsciiDoc, a text document format for writing short documents, articles, books and UNIX man pages that can be easily translated to HTML and DocBook markups. It is really easy to get the hang of it, so if you want to contribute, please take a look at the AsciiDoc Cheatsheet and start editing the documentation sources right ahead. They are distributed with the source code and are located under ./doc of the source tree. If you don’t have SVN access, simply mail your contributions to feedback@cherokee-project.com.
Yes. Since content encoding is set on a per-rule basis, simply add a rule at the beginning of the virtual server that matches the specific file extensions and has the encoding enabled. Set the rule to be non-final. That should do the trick.
First, make sure openssl in installed. If you are not installing from source, most likely you’ve missed installing libcherokee-mod-libssl
The answer is yes. Please refer to the Upgrading Cherokee section of the documentation.
Make sure you are building it with gmake.
PHP is configured by default to limit the size of uploaded files. Check the PHP upload limits note to tweak the appropriate settings.