| 1 |
== link:index.html[Index] -> link:basics.html[Getting started] |
|---|
| 2 |
|
|---|
| 3 |
Requirements |
|---|
| 4 |
------------ |
|---|
| 5 |
|
|---|
| 6 |
[[hw]] |
|---|
| 7 |
Hardware |
|---|
| 8 |
~~~~~~~~ |
|---|
| 9 |
Cherokee is very light, completely modular and it can be tailored to |
|---|
| 10 |
your specific needs. As such, disk requirements will vary depending on |
|---|
| 11 |
the options selected for the building process. A static build for |
|---|
| 12 |
embedded devices can occupy as little as 200KB, give or take. |
|---|
| 13 |
|
|---|
| 14 |
In terms of processing power, it has been known to work with as |
|---|
| 15 |
little as 133Mhz ARM processors. It could very well work on something |
|---|
| 16 |
smaller, but we haven't really had the chance to try it out. |
|---|
| 17 |
|
|---|
| 18 |
[[sw]] |
|---|
| 19 |
Software |
|---|
| 20 |
~~~~~~~~ |
|---|
| 21 |
Cherokee has no dependencies besides a standard libc. Everything else |
|---|
| 22 |
is optional. Obviously anything beyond mere static content serving |
|---|
| 23 |
must be available for Cherokee to correctly execute the task. This |
|---|
| 24 |
means you will need PHP if you want Cherokee to serve PHP dynamic |
|---|
| 25 |
content, MySQL or LDAP development libraries if you want built-in |
|---|
| 26 |
support for these as authentication mechanisms for protected content |
|---|
| 27 |
and so on. |
|---|
| 28 |
|
|---|
| 29 |
|
|---|
| 30 |
If you intend to build Cherokee from source however, you will need |
|---|
| 31 |
several tools and libraries. |
|---|
| 32 |
|
|---|
| 33 |
* Building tools: Cherokee is built on top of the autoconf and |
|---|
| 34 |
automake tools, hence your systems has to have some basic system |
|---|
| 35 |
programs like an sh shell, make and an ANSI C compiler. We have |
|---|
| 36 |
compiled Cherokee in various platforms with different compilers, so |
|---|
| 37 |
it shouldn't be a problem. |
|---|
| 38 |
|
|---|
| 39 |
* Python: Cherokee has an administrative web interface written in |
|---|
| 40 |
Python, so if you intend to use cherokee-admin you will need this. |
|---|
| 41 |
For disk space constrained environments this won't be an issue |
|---|
| 42 |
since you would probably want to make a minimal install in your |
|---|
| 43 |
destination host, preconfigured elsewhere. This programming language |
|---|
| 44 |
is also used to generate the documentation, and Cherokee includes a |
|---|
| 45 |
number of Quality Assurance tests written in it as well. If you are |
|---|
| 46 |
planning to contribute code into the project, or you just want to |
|---|
| 47 |
test everything is working in the server, you will need a Python |
|---|
| 48 |
interpreter installed on your system. |
|---|
| 49 |
|
|---|
| 50 |
* If you are building Cherokee in a non-POSIX compliant platform such |
|---|
| 51 |
as Windows, you will need a POSIX threads implementation. You can |
|---|
| 52 |
disable the usage at compilation time and do without this, though, |
|---|
| 53 |
but this has a dramatic impact in scalability. |
|---|
| 54 |
|
|---|
| 55 |
* If you want to make a build that serves secure content, you will |
|---|
| 56 |
need TLS libraries. Cherokee ships with support for the OpenSSL |
|---|
| 57 |
backend, but the architecture is completly modular and any other |
|---|
| 58 |
backend can be implemented. You need to have the development files |
|---|
| 59 |
of the chosen backend libraries in order to build a package that |
|---|
| 60 |
suits your needs. |
|---|