Tag Archives: apachecon

Apache Web Server training, mod_rewrite training

I’ll be teaching two training classes at the upcoming ApacheCon in Atlanta in November.

On Monday, I’ll be teaching Apache, Nuts to Bolts, with Jim Jagielski, another long-time contributor to the Apache httpd project. This class is a day-long training on everything from obtaining and installing the server to configuration, third-party modules, and security, and everything in between.

On Tuesday, I’ll be teaching a half-day training onmod_rewrite, the most powerful, and probably most confusing module, and the source of the majority of questions on any given Apache support forum.

I’d love to have you in my classes. ApacheCon will be fun, as always, and Atlanta is a great city. We’d love to see you there.

mod_rewrite docs rewrite at ApacheCon

The plan, (assuming I don’t get sidetracked on a million other things, which is what usually happens) is to do a major overhaul of the mod_rewrite documentation during the hackathon at ApacheCon. Please speak up if you have specific comments or recommendations. So far, the outline is something like this.

1) A couple of years ago, I split the “Rewrite Guide” into basic and advanced. This was ill-advised, and the division was stupid. Now it’s just harder to find stuff. Going to re-merge those, and then try to do a division based on topic, rather than difficulty, since that’s not a particularly useful concept.

2) Rewrite cookbook, divided into categories of, perhaps:
a. redirecting/remapping
b. controlling access
c. when not to use mod_rewrite (aka ‘mod_rewrite is obsolete’)
d. advanced features

3) Scrap the inscrutable examples. Both the guide and the formal docs are littered with examples that either never happen in the real world, or are done better using some of the built-in functionality of other modules like mod_alias and mod_dir. Scrap those examples entirely, rather than continuing to try to make then scrutable.

4) Rewrite Flags documentation. Started this years ago, and never really finished it. Also, needs to be updated to include the new flags that have been added in 2.2 and trunk.

5) General grammatical overhaul, hopefully with help from Noirin, who has better grammar than all the rest of us put together. (Actually, that’s the problem – it was written by all of the rest of us put together, resulting in a mish-mash of styles and voices.)

6) A document about (so-called) S.E.O. uses of mod_rewrite, discussing both the techniques that can be used, and the misinformation that tends to drive the desire to use those techniques. This needs to be handled carefully, because there’s a tendency to simply state that all SEO is snake oil – which much of it is – and ignore the topic entirely. But, folks are going to do this stuff whether or not we approve, and it’s better if they do it well. At least, that’s what I think at this particular moment.

2c, above, is both about stuff that you shouldn’t do with mod_rewrite at all, and also some of the new features in 2.2 and trunk that make mod_rewrite unnecessary.

Tomcat at ApacheCon

Tomcat is one of the oldest members of the Apache family, and one of the standard building blocks of the web as we know it today. It can sometimes fall below the radar, because it just works, so most folks are completely unaware of it.

Filip Hanik will be doing a training class on Tomcat at ApacheCon this year. I spoke with him last week for Feathercast, and I’ve finally edited it. You can listen here, or come to ApacheCon and hear him there.

Apache HTTP Server – Nuts to Bolts

ApacheCon is just a few weeks away. Jim and I are doing our Nuts to Bolts training class again, with all new content, because of all the cool new stuff that has gone in to Apache over the last year. Don’t miss it!

A two-day training covering everything you need to know to administer an Apache HTTP Server.

Day one, led by Jim Jagielski, give the overview of the server, showing you the core architecture of the server, how the modular nature of the server works, and shows you the most important of the modules. You’ll learn how to install the server, how to configure it, secure it, and performance-tune it.

Day two, led by Rich Bowen, takes a more hands-on, recipe driven approach. You’ll learn how to accomplish common tasks, install third party modules, and troubleshoot common problems. Examples are taken from questions often asked on the support mailing lists and IRC channels.

Jim and Rich have both been working with the Apache HTTP Server for more than ten years, and have both taught training classes for many of those years.

ApacheCon day … something

Yesterday, I felt absolutely wretched. This used to happen to me a lot at conferences. I’d get sick the first day or two, and miss a lot of stuff. I spent most of yesterday napping.

I feel a lot better today, but am still very tired.

This afternoon – in about 2 hours – I’ve got my mod_rewrite presentation, and then tonight I’m MCing the Lightning Talks, since Fred and Fitz aren’t here this year. Could be fun. You should come.

ApacheCon Day Two

The first night in Amsterdam, I went straight to sleep, so yesterday was pretty good. Last night, I was up almost all night, or so it seemed, and today I am exhausted. Which is bad, because I have to talk all day long. I’m going the second day of the “Apache Nuts To Bolts” training class. JimJag did day one.

The presentation bit is here. Yeah. I know. Comic Sans. Get over it.

Lunch was great, but now I’m tired *and* full, so the afternoon is going to be a little long. Just 3 hours to go.

In Amsterdam

I’m in Amsterdam again. ApacheCon starts tomorrow, and I’ll be doing a two-day Apache HTTPd Server training class with JimJag.

I slept quite a bit on the plane, which was unexpected. So I’m going to try to stay up instead of napping, so that I can sleep tonight. Perhaps I’ll take a stroll downtown – perhaps as far as Rembrandt Platz. But now that I’m deciding to go somewhere, I’m starting to feel … very … sleepy.

Ready to go …

This year, preparing for ApacheCon has been unusual. I guess it changes every year, but this year I really would rather be staying home. Don’t get me wrong, I’m sure that the conference will be fabulous. It always is, both as a technical conference, and as a time to catch up with longtime friends. But the trees are just starting to green, and it’s warming up, and I will miss my family an awful lot. And I’m just not that exited about Amsterdam. I’ve seen Amsterdam. I’ve seen the bits that truly interest me, and may try to go to the Van Gogh museum again this year, if I have time. But I don’t care for the red light district, and I don’t care for the coffee shops, and I don’t have a lot of cash laying around to spend on the admittedly amazing restaurants, so I expect to spend most of the time in the hotel working on long-past writing deadlines, which I’d really rather do in my own home.

That said, I’ll say again that I’m sure the conference will be amazing, and as soon as I get there and get immersed in it, I’ll have a good time. Just not real fired up about it right now, with just 4 hours left before I need to leave for the airport.

I wonder if I packed my toothbrush …