Apache Cookbook 2nd Edition 42
stoolpigeon writes "The Apache web server has been the number one http server on the internet since 1996. It has also become an integral part of many open source and proprietary software systems. It runs on diverse hardware, in locations all over the globe, hosting sites large and small. In November of 2003 Ken Coar and Rich Bowen had their "Apache Cookbook" published by O'Reilly. The duo brought years of experience in working with and documenting the Apache server to the plate. Now, over 4 years later they have published the second edition. Four years is a long time, but it would be reasonable to ask if this new edition is worth purchasing, especially if one already owns the first edition." Read below for the rest of JR's review.
The answer is of course, it depends. After I read the new edition I sat down with a copy of the first edition so that I could compare the two. The most obvious and easily noticed difference is that the second edition is larger. Including the index, the second edition is 51 pages longer. This does not mean that they just tacked on 51 more pages of material. A small amount of material was dropped from the first, sections were added to almost every chapter in the second, and an entirely new chapter was added to the second. I think that this bodes well for the new edition as it indicates that the authors did not just slap a few new pages in place to cover some new features, or do a quick search and replace on version numbers. There is a decent amount of repeated material, but only where there have been no changes needed. | Apache Cookbook 2nd Edition | |
| author | Ken Coar and Rich Bowen |
| pages | 285 |
| publisher | O'Reilly Media, Inc. |
| rating | 8 |
| reviewer | JR Peck |
| ISBN | 0-596-52994-5 |
| summary | Solutions and examples for Apache Administrators |
The authors state that every recipe comes from real world needs, either working problems on their own or helping others. I am sure that this approach is what drove many of the changes. Sections that are no longer applicable or don't seem to come up as often could be dropped to make room for new issues, or issues that have come up with a higher frequency. The new content as I mentioned is spread out throughout the book. For example, the first chapter "Installation" originally had 7 sections and now has 13. This is due to additional sections on things like installing on Debian based machines, which version of Apache to use, and more sections on downloading and then installing Apache from source.
The new chapter is "Directory Listings". There are 20 sections or 'recipes' that deal with displaying directory/folder listings and modifying the same. Only four chapters do not add more sections in the second edition. Of those only two still contain the same recipes, the other two have had some dropped and others added. Of those two, I checked the various problem solutions and found that while there were many similarities, links to documentation and resources had been updated as well as fixing the recipe if needed. This book has been very thoroughly overhauled.
While the information given is often new, the format, layout and writing are very consistent with the first edition. This means the strengths of the first book carry over as well as some of the weaknesses. The issues I had with the book are that much of it will seem rather simple or basic to the admin who likes to dig into documentation, or is already familiar with installing and managing software. This may be a great thing for the novice or someone trying to install Apache on a platform they don't normally use. (Whether that is Linux or Windows. The Linux install instructions are very brief; the Windows instructions include screen shots and take up more room but cover the whole process. Might be handy for anyone who must install Apache on Windows, but unfamiliar with the OS.) But for the experienced Apache or System Admin it may feel unnecessarily simplistic at times. For example, a new section from the first chapter has added how to download the source along with installing from the source.
Another thing I found awkward is when problems were presented with no solution. I guess the question has come up enough for the authors to feel it deserved being addressed in the book, but in both editions there are times when the solution is literally, "No solution is available with standard Apache features." The authors do take the time to explain why this is so, and the issues involved, but it felt odd nonetheless. The discussion and "See Also" sections will probably be helpful, but this just brought to the forefront that often administration of software is a lot more than just recipes in a cook-book.
I think it is safe to say that if you have or have read the first edition and are still using it, it may be worth your time to check out the full table of contents on the second edition. There may be some new things here that could really come in handy and make it worth picking up this new volume. If you didn't like the first edition, I doubt you will be too crazy about the new one. If you haven't been exposed to the first edition but are new to Apache, or find yourself struggling with Apache, this may really be a great help. For the experienced Apache admin, I would again recommend checking out the table of contents. It shouldn't be too difficult to see if there is something worthwhile here. With such knowledgeable authors, I think that readers will find good advice if there is an area where they need it.
I really doubt there is anything here that can't be found online. Apache's popularity and wide use mean that there is a lot of information out there. The problem is of course that this abundance of information makes it difficult at times to track down what is best or at times what is even accurate. In this book the reader gets the experience and knowledge of two experts in the subject matter, nicely laid out before them. For the person who values quick and accurate information over spending time sifting, this book provides just the time saver that they want.
The index is solid, and the table of contents really breaks things down so finding things is very easy. Like many new O'Reilly titles, this comes with 45 days of access to the book in electronic format through Safari.
You can purchase Apache Cookbook 2nd Edition from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
Re: (Score:2)
Re: (Score:2)
Maybe nginx [nginx.net]? highscalability.com has an article about a popular Rails Facebook app [highscalability.com] that replaced a hardware load balancer with a dedicated nginx box. 10M hits a day, not bad.
Re: (Score:2)
to address the GP: it isn't clear (to me, at least) what the successor to Postfix will be. There is no successor thus far which makes Postfix look thoroughly old-fashioned.
Re: (Score:2)
You're right, I misunderstood the post. I thought the question was "what's the successor to Apache that will do for Sendmail what Postfix did - e.g., make it obsolete?"
Re: (Score:2)
Re:Today's Apache is Tomorrow's Sendma- Redundant? (Score:2, Informative)
Re: (Score:2, Funny)
Re: (Score:2)
Re: (Score:1)
Re: (Score:2)
In this case it's a clear case of trolling, but hell, as long as they mod it into oblivion, I don't particularly care. In all honestly, I only ever look at +x funny as a special marker. I don't look at -x articles except when meta-moderating,
My suggestion (Score:3, Interesting)
Re:My suggestion (Score:5, Insightful)
Re: (Score:2)
That's not a jail by any definition.
Re: (Score:2)
Re: (Score:2)
Again, where is the security benefit of cgi-bin either way?
Re: (Score:2)
Re:My suggestion (Score:4, Funny)
Re: (Score:2)
http://perl.apache.org/download/index.html
Apache cookbook summary of summary: (Score:2)
Re:Apache cookbook summary of summary: (Score:5, Funny)
1 cup Apache
3 Tbs Linux (note that linux comes in many flavors and chef should select to taste)
a dash of GUI selection
Let server simmer and slowly add Linux to taste
Dress and add Apache - let bind.
Extract and add GUI selection.
Garnish and serve!
Note: Linux can be fatty depending on cut. If desired, user can trim as necessary.
Re: (Score:2, Funny)
You have to be careful these days when posting things involving enumerations of random things and one cup.
I almost tried to imagine... oh nevermind.
What's cooking? oh wait (Score:1)
bleh (Score:1, Informative)
i run several sites and 2 are bigger than slashdot
and we use lighttpd and nginx with php running as fast-cgi
the switch literally means we need to rent less servers now! and the sites are alot snappier
Re: (Score:2)
Re: (Score:2)
Alternative web servers? (Score:1)
If all you need is mod_rewrite help... (Score:2)
a chapter on directory listings? (Score:2)
Table of contents (Score:2)
Looks like most of the sections are obvious to anyone experienced with Apache (as I am, I support it at work). But a few things in there may be worth getting my hands on a copy.