For those of you that care about what makes the org tick... (Bart was asking, for one.)

Server
- VA Linux 2U rackmount case
- Dual P3-450 CPUs (Katmai build)
- 1G RAM
- SCSI disk subsystem (9G, 18G)
- 100baseT ethernet

Uplink
- Fiber channel to multiple redundant backbones
- Hosted at Equinix
- Locally switched through Foundry Networks ServerIron

Operating system
- Started out as Debian GNU/Linux
- Linux 2.4.13 (custom tweaked kernel)

Software
- Webserver: custom-built Apache 1.3.22
- Scripting: PHP 4
- Script caching: APC
- Source control & release management: cvs and rsync
- Database: MySQL 3.23
- Full-text indexing: mnogosearch

Code
- All "livesite" code is in PHP. No more perl involved in user-interaction.
- Site is 99.9% custom; aside from approx 300 lines of code taken from the phpBB project (for message code formatting), it's completely original. If there are bugs, let me know.

Notes
- All prince.org content is "instantly" backed up to a remote location via database mirroring. The prince.org site runs off a clone of the latest site code, which is not stored on the same machine. This makes restoring service in case of catastrophe, much easier. In general, prince.org is designed to run more robustly than a lot of small enterprise sites you may visit.
- prince.org uses a custom database caching engine to minimize load on the database. The homepage is typically rendered with no queries to the DB for standard content, making the 2.0 homepage about 20X faster than the 1.0 homepage to render, while containing hugely more information.
- I do/have develop/ed professionally in C, C++, Perl, PHP, Java, VisualBasic, etc., for more than 10 years. I've chosen the tools I have for prince.org because I like the philosophy of Open Source, and I find them fun to work with.

Just the facts, man.

WOW, this means absolutely nothing to me! WTF is a kernel?!

thanks ben

ben said:

U one clever dude ben. I thought I was a webdesigner till I read this lol