Cherokee is a high-performance web server. It is very fast, flexible and easy to configure. In fact, it is the fastest web server there is. It offers support for the widespread technologies nowadays: FastCGI, SCGI, PHP, CGI, SSI, TLS and SSL encrypted connections, Virtual hosts, Authentication, on the fly encoding, Load Balancing, Apache compatible log files, Data Base Ba-lancer, downtime-free updates and upgrades, Reverse HTTP Proxy, and much more.
Unlike many other web servers out there, Cherokee gracefully handles many concurrent connections, has a low memory footprint, and provides load balancing facilities. As such, it is suitable for usage among a wide variety of systems, from tiny embedded devices to huge enterprise grade infrastructures. It is also multi-platform, offering native performance for Unix, Linux and Windows systems.
Cherokee Installation:
Open the terminal and type following command:
Start cherokee-admin by issuing the following command:
You will obtain an output similar to the following one, which provides the information needed to be able to access the configuration interface (username & one time password). This information is generated randomly each time the program is launche, and it can be very useful in case you need to to give temporary access to a remote administrator in the confidence that no future accesses will be possible.
Then redirect your web browser to 127.0.0.1:9090, which is the default address and port for the administration interface. The User and One-time Password will be required initially. This is to prevent other users of the local host from being able to configure the server unless they have access to the password.
Home: This is the initial screen of cherokee-admin. From here you will be able to launch and stop the web server, change the language of the configuration-interface, check a quick view of the server status and access relevant support and contact Cherokee-Project links.
Status: This gives access to usage graphs and statistics regarding each virtual host and the server as a whole.
General: There are a number of entries that specify the most significant configuration options such as the port - or ports - that the server will listen to, the default timeout, whether to support keep-alive connections, default icon and MIME type definitions and so on.
vServers: If you want your web server to work with more than one domain you will have to create Virtual servers other than the default one. Each one will have a completely independent configuration: paths, behavior, logging facilities, etc.
Sources: Define the resources that will be providing information. For instance, PHP.
Advanced: This is to configure the most complex parameters of the server and how it interacts with the operating system. If you are unsure about any of the options here, better not mingle with them. Default values should work just fine.
If you are looking for development information relevant to your automation and scripting needs, you should refer to the appropriate section, specifically the /etc/cherokee/cherokee.conf file specification.
Unlike many other web servers out there, Cherokee gracefully handles many concurrent connections, has a low memory footprint, and provides load balancing facilities. As such, it is suitable for usage among a wide variety of systems, from tiny embedded devices to huge enterprise grade infrastructures. It is also multi-platform, offering native performance for Unix, Linux and Windows systems.
Cherokee Installation:
Open the terminal and type following command:
sudo apt-get install cherokeeAmong its many features there is one that deserves special credit: a user friendly interface called cherokee-admin that is provided for a no-hassle configuration of every single feature of the server. This administration interface allows you to configure the web server without having to worry about editing a text file written with a certain syntax.
Start cherokee-admin by issuing the following command:
cherokee-admin -b &This instructs the cherokee-admin program to bind to all IP addresses so it may be reached remotely. It will be launched in the background, so you'll still be able to use your SSH session.
You will obtain an output similar to the following one, which provides the information needed to be able to access the configuration interface (username & one time password). This information is generated randomly each time the program is launche, and it can be very useful in case you need to to give temporary access to a remote administrator in the confidence that no future accesses will be possible.
Then redirect your web browser to 127.0.0.1:9090, which is the default address and port for the administration interface. The User and One-time Password will be required initially. This is to prevent other users of the local host from being able to configure the server unless they have access to the password.
Home: This is the initial screen of cherokee-admin. From here you will be able to launch and stop the web server, change the language of the configuration-interface, check a quick view of the server status and access relevant support and contact Cherokee-Project links.
Status: This gives access to usage graphs and statistics regarding each virtual host and the server as a whole.
General: There are a number of entries that specify the most significant configuration options such as the port - or ports - that the server will listen to, the default timeout, whether to support keep-alive connections, default icon and MIME type definitions and so on.
vServers: If you want your web server to work with more than one domain you will have to create Virtual servers other than the default one. Each one will have a completely independent configuration: paths, behavior, logging facilities, etc.
Sources: Define the resources that will be providing information. For instance, PHP.
Advanced: This is to configure the most complex parameters of the server and how it interacts with the operating system. If you are unsure about any of the options here, better not mingle with them. Default values should work just fine.
If you are looking for development information relevant to your automation and scripting needs, you should refer to the appropriate section, specifically the /etc/cherokee/cherokee.conf file specification.
0 comments:
Post a Comment