Slashdot Mirror

We use Apache Toolbox" to build Apache, it's a nice menu driven way to configure/customize Apache. There is a place to make the changes under "apache" then "hacks". Even if you don't what to change what Apache reports as it's type, I recommend using this project as it make compiling a customized version of Apache almost fool proof!!!

I've done the roll-your-own apache/mod_perl/mod_php/mod_etc.etc.etc... thing before. I'd love to have those hours of my life back. So if the Apache foundation really cares about evangelizing 2.x why don't they create something as powerful as ApacheToolbox that actually works with 2.x?

If your OpenLDAP/Kerb5 kit was put together right, you could use the LDAPv3 setup for authenticating more standard clients, and use pGINA for Windows. It won't kerberize you (yet), but SSL should provide your basic security. Samba servers using the LDAP backend should fit quite nicely.

Another idea is to configure LDAPv3, and set up a Samba server(with the LDAP backend) as a Domain Logon server. If these are all on one server, you've pretty much built the same thing Microsoft does on an AD PDC, but without the tight integration. LDAP clients get the full benefit, and Windows clients will work out of the box. Think of it like half-assed AD. :)

What would be nice is to see something like Apache Toolbox for OpenLDAP and Kerberos. LDAPv3 is quite a task to get set up, and I think the huge learning curve for the system is it's largest flaw. Seriously, Microsoft only needs to know your dns domain to get everything configured, why can't it be that easy? :>

Short answer: Because of it's legacy and partially because 2.x isn't a revolutionary step forward and it took a while for 2.x to get out of beta. Also, 2.x probably benefitted the Windows platform and new module writers moreso than anyone else, IMHO.

1.3x is what most people know, what most Apache modules are written for, and what most of the articles and tutorials on the web describe.

Another example: Apache Toolbox still only compiles 1.3x and associated modules for you. (BTW: this is a great resource for trying new modules out when you can't find an RPM with what you need.)

It's only now that I'm migrating production from 1.3x to 2.x, because I had seen that people had headaches getting PHP working (but no longer) and I waited for stable ports of some modules that I used in 1.3x.

I do consider 2.048 to be worthy now, lots of RPMs and modules written for it.

The strangness that various distros impart to apache is why I usually start with Apache Toolbox. This uses wget to automatically download any missing source, and currently supports 60+ third party modules in addition to the 36 apache modules which are included in standard source distribution. For redhatters, this even halts appropriately for RPMs that cause problems. Works on slowaris, and pretty much any BSD/*NIX with gcc. I'm not a member of this project or anything, just a fan: it just works.

Another tool is ApacheToolbox.

I agree with you. Editing by hand is the way to go.

Apachetoolbox supports mod_gzip.

Apachetoolbox

Apachetoolbox actually installs everything from the original sources. It supports apache, mysql, php, over 60 modules for apache. Opensource to.

-io

Check out Apache Toolbox. Way less than half a day.