I’ve configured Apache for virtual hosting on more sites than I can count, but I’ve always just kind of stumbled through until now. What’s changed? The Apache 2.2 documentation is worlds better than the old 1.3 docs (even though the old docs rank highest in Google). So here they are: name-based virtual hosts, plus virtual host configuration examples (including an example mixed name and IP virtual hosting, which is what I needed), and some tips on dynamically configured mass virtual hosting.

“Apache is like Microsoft Word, it has a million options but you only need six. Nginx does those six things, and it does five of them 50 times faster than Apache.” –Chris Lea.

Why? No forking. No loading of unnecessary components. Fast CGI. And to prove it’s not as complex as you might think, he’s installing it live. The session has eight minutes left, can he do it?

Yes, he did. The big concern is in managing permalinks without .htaccess, and it turns out it’s not so difficult. Does he have a cookbook for this? Darn, no time left for questions, I’ll have to ask later.

p0ps Harlow tweeted something about trying to get an AMP environment running on his Mac. Conversation followed, and eventually I sent along an email that look sorta like this:

If you’re running 10.4 (I doubt it, but it’s worth mentioning because I’m most familiar with it), here’s how I’ve setup dozens of machines for web development and WordPress:

Install MySQL
http://dev.mysql.com/downloads/mysql/5.0.html#macosx-dmg

Install Marc Liyanage’s PHP 5 package
http://www.entropy.ch/software/macosx/php/

From there all you have to do is install WordPress.

10.5 changed lots of this (as you probably already know). The good news is that it includes current versions of the AMP suite. The bad news is that the PHP doesn’t include a number of useful components. Still, it will run WordPress and I’ve got it working on my laptop. These directions look like pretty much what I had to do:

http://stringfoo.com/2007/11/05/server_setup_on_leopard/
http://remysharp.com/2007/10/27/lamp-in-leopard-osx-105-php5-and-apache-22

It’s likely none of that will be helpful, in which case you will have discovered why I’m no longer a sysadmin.

Marc Liyanage’s builds of PHP for Mac are probably the easiest to use and they include most all the extensions a person could want, but he hadn’t released a package for Leopard at the time (he’s got a release in beta now). As it turned out, p0ps actually was running 10.4, and he got things going in a jiffy.

Yep. Leopard comes with new stuff. Lazeez says it works fine, but commenters here are having trouble.

leopard, Mac OS X 10.5, apache, php

I’m lazy, that’s all I can say to explain why I hadn’t put any serious thought into upgrading from the 1.3.x version of Apache that ships with Mac OS X to the much more feature rich 2.0.x or 2.2.x. But today I found reason enough to switch my development to 2.2.3, and I went looking to the community for information about the switch.

A post in Marc Liyanage’s forums made it clear how easy config/compile was. Minutes later I was up and running and fiddling with the new features.

Mac OS X, apache, apache 2.2.3, mac, web server

My Sun T2000 is here, and with Cliff’s help it’s now patched, configured, and online. (Aside: what’s a Sun Happy Meal?)

I’ll second Jon’s assessment that Sun really should put some reasonable cable adapters in the box, as the the bundle of adapters necessary to make a null modem connection to the box is ridiculously out of scale (I’ll get a picture soon).

I’m getting the application environment put together, which has turned out easier than expected thanks to the convenient packages from Blastwave.org. The box came with Solaris 10 installed, and after a quick installation and configuration of pkg-get I was happily installing Apache, MySQL, and PHP as simply as typing pkg-get -i apache.

AMP, AMPS, Apache, Blastwave.org, LAMP, MySQL, PHP, Solaris, Solaris 10, Sun, Sun Microsystems, T2000

A Solaris sysadmin I’m not. But now that I’ve finally got the Sun T2000 server I begged for a while back, I’ve got to ramp it up right quick.

The first task is to get a, um, LAMP environment up and running (SAMP?…oh, Sun wants us to call it AMPS). A bit of Googling turned up this forum thread that suggested Blastwave.org’s ports of PHP, MySQL, and Apache.

edit: I corrected the model number.

amp, amps, apache, lamp, mysql, open source, oss, php, solaris, sun, t2000

Between WordPress 1.x and 2.x there was a big change to the way rewrite rules are handled.

In the old days, everything got written out to a .htaccess file. Every condition, every form of permalink could be found there, and I had some comfort knowing I could see and mess with it all. I was a bit surprised to find that with 2.0.2, WP writes out a sparse file that has only one significant rule. Something that looks like this:

RewriteRule . /blog/index.php [L]

That one line takes everything in your request URL and passes it through to index.php for processing. The beauty of this is that WP doesn’t need to write to the file system with every change to the permalink structure (which used to include every new “page” added or renamed).

The only downside to this is that you can no longer expect a $_REQUEST array full of all the query terms your plugin might use. Instead you’ll have to use the $wp_query object. All of this was probably mentioned in the API docs before I built a bunch of dependancies on $_REQUEST, but it was easy enough to fix.

$wp_query, $_REQUEST, .htaccess, apache, apache rewrite, rewrite rules, wordpress, wpopac

Or, er, my server will be crushed. I guess I should admit that my stuff could do with some optimization, maybe. Perhaps what I really need is something faster than Celeron with 512MB RAM. Maybe.

tags: 512mb ram, apache, break point, breaking point, celeron, crushed, load average, mysql, php, server, top, web server

I do a lot of web development on my laptop. I’ve got Apache and PHP there, so it’s really convenient, but I usually move projects off to other server before I get around to wanting to mess with mod_rewrite. Not so, recently, but I ran into a big stumbling block when I discovered OS X’s Apache comes pre-configured to ignore .htaccess files.

A couple points. First, Apache’s own mod_rewrite docs include the following quote:

Despite the tons of examples and docs, mod_rewrite is voodoo. Damned cool voodoo, but still voodoo.

So I’m not going to feel too bad about scratching my head for a minute before realizing I should check to make sure the httpd.conf file had support for .htaccess files enabled, but the second point, and I know this thanks to Richard Rutter’s Clagnut, support must also be enabled in the user’s http.conf file (located in /private/etc/httpd/users/). For full details, go read Rutter’s enabling .htaccess in OS X post.

tags: .htaccess, apache, apache http server, apache web server, docs, enabling .htaccess files, httpd.conf, mac, mac os x, mod_rewrite, os x, richard rutter

Be geeky and look at the Apache modules:

/usr/sbin/httpd -l
Compiled in modules:
core.c
prefork.c
http_core.c
mod_so.c

Set your path:

PATH=$PATH:/usr/sbin
export PATH