Roberto Correa dijo [Thu, Jan 15, 2009 at 02:32:14PM +0100]:
> Hi,
>
> I post a Table of Contents Draft of the future Cherokee book that we have
> created.
>
> This version is translated to English in order to spread the contents and
> for people to participate with comments, suggestions,etc..
> (...)
Nice initiative, thanks!
> ===================
> 2.CHEROKEE INSTALLATION
> ===================
> 2.1.- Hardware and software requirements
> 2.2.- How to download Cherokee's source code
> 2.3.- Unix/Linux installation from sources
> 2.4.- Linux installation from binaries
> 2.4.1.- Debian installation
> 2.4.2.- Ubuntu installation
> 2.4.3.- RedHat/Fedora/Mandriva installation
> 2.4.4.- OpenSuse installation
> 2.4.5.- Gentoo installation
> 2.4.6.- ArchLinux installation
> 2.4.7.- T2 installation
> 2.5 Unix installation from binaries
> 2.5.1.- OpenBSD installation
> 2.5.2.- FreeBSD installation
> 2.5.3.- NetBSD installation
> 2.6.- Windows installation
> 2.7.- Install the latest build from repository
> 2.8.- Upgrade Cherokee from a previous version
> 2.9.- Uninstalling Cherokee
> 2.10.- Running Cherokee
Keep this one simpler. 2.4.* and 2.5.* can be summarized to "follow
the usual install procedure in your operating system of choice", or
just including a simple table detailing any known
specificities. Besides, this would be highly volatile content - If you
ever have such a book in your hands and it lists i.e. URLs to download
from, they will surely be obsolete.
> =================
> CHEROKEE MONITORING
> =================
> 1.- Log Files
> 2.- Server Info
3.- Gathering information about the server from the OS (think
i.e. finding the PID, live resource consumption monitoring, making
sense of whatever you can find via gdb, in /proc or via strace,
dtrace or whatever is adequate in a given OS).
> ===========
> FRAMEWORKS
> ===========
> 1.- Setting up Rails on Cherokee
> 2.- Setting up Django on Cherokee
> 3.- Setting up Kumbia on Cherokee
> 4.- Setting up Zend on Cherokee
>
> ============================
> THIRD PARTY DEVELOPMENT PLATFORMS
> ============================
> 1.- Setting up PHP on Cherokee
> 2.- Setting up ASP.NET on Cherokee
> 3.- Setting up Glassfish on Cherokee
>
Instead of focusing on specific frameworks (which, of course, will
evolve away from what is printed - At least I have long suffered that
the Rails people cannot stand on a given configuration for over a
couple of months because it starts itching), I'd reword this point as
"interacting with application servers" - where such frameworks, as
well as Jboss/Jakarta, ASP.NET and myriads of others fit in
better. But not as much going into describing how to set up a Zend
project behind a Cherokee webserver - Focus instead on why it is done
that way. As an example, for a long time I wrote my systems using
mod_perl. But it tied me so ruthlessly to Apache, and exposed all of
Apache's guts to me, and imposed a broken security model (i.e. all
systems run under the same UID, which is the same as the webserver
itself's). When I started doing Rails, I started via the same path
(running under Apache with mod_fcgid, or what they are doing nowadays
which is also b0rken, via Passenger/mod_rails), until I realized
running a separate server (Mongrel in this case) is way better.
Thanks for your work!
(now, get moving and write. I want the book on my desk by Monday)
--
Gunnar Wolf - [email protected] - (+52-55)5623-0154 / 1451-2244
PGP key 1024D/8BB527AF 2001-10-23
Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee
