I wanted to upgrade apache, but just don't know where to start.

One of the best things to do, is to locate all the source for all the modules you currently have in your current version of Apache and make sure you get them and build them properly, in the proper order and any components those modules will need as well. For some modules you might have in Apache now, you might need to not only download the source to build those modules (or the newest, stable versions of them anyway), but those might require you have source or other thins installed. It also depends if you use a lot of dynamically loaded modules, or if they are built into Apache's core. For example, you can't load in the SuEXEC CGI wrapper, you have to compile Apache with it in Apache's core. PHP doesn't need to be a core module, although I prefer it to be. Sure, it's not as dynamic (as DSO), just as mos_ssl isn't if you have it as a core module, but it's sometimes more efficient I've found. Anyway, things like PHP often require more than just compiling them, as you sometimes have other modules, like GD, jpeg-dir, imap, etc. Often though, you can just declare the path to them. Some things like mod_ssl require you to at least have openssl and perhaps some other items, to properly build mod_ssl, if you use that, and depending on how you use it. You might need or want certain things for that. Also, be aware of other things, such as other modules, like if you have mod_frontpage (which I can not stand!) and that sometimes they are behind on development and it won't work properly with the newest Apache server that's currently released and stable. It's good to keep up on all the newest versions for stability reasons and security reasons. PHP is important to keep up on, for example. Other things are as well.

So, consider not only what you have to do to accomplish an upgrade, but what things that the things you know you need might possibly need (I know that sounded like it was worded strangely). Finally, consider on what other modules or components you might want to add. Plan well, it's not that difficult and it doesn't take too long, but it's not that quick either and things like RPM's will likely be a bad idea, and you want to make sure you can change/modify things later and recompile it if you have any changed you nee to want to make, any adjustments or most importantly, anything you want to remove or add. This (having the source and build history) will make it a lot faster and easier on your next upgrade/modification -- and that will happen. As for where you should start, that depends on what you have, what you want and what you need. My suggestion is to download the sources you need from their respective web sites and read, plan and read, if you're not sure and already know exactly what to do and how. Next time, you will know exactly and the more you do it, the more you'll know -- and you'll know exactly when and where and why you want to or need to make a change or addition to any part of your web server. You'll also start making more wise and experienced choices, like when to change something or when to just upgrade other things, etc. This ideal should be practiced for any aspect of a web server though, of course. This is one aspect that you get good at by doing and you just improve more and more -- even by avoiding stupid mistakes and oversights that can cost you time and headaches... pretty soon, you'll be wondering how you ever made those little mistakes (unless you're smart enough to be careful and attentive and to read before you do). I know this wasn't helpful as far as steps go, but there's no way anyone can answer without guessing.

Oh, and of course, besides making sure you gather all the things to make your current configuration still work, backup your apache directory and make sure you can revert back to it, even via a symbolic link temporarily, if needed. After all, you don't want to wipe out your last binary's and whatnot and then _have_ to learn how to make it work the hard way if you want a web server again. Finally, be careful, because some configurations and some tools' configuration can open up security or performance issues if they are not configured or installed properly, either during or after the build(s), of course. Look at it as if you're upgrading a kernel, you don't want to lose any of the drivers, or the kernel might fail to work and even allow your system to boot, just as Apache might not start up again, if you don't upgrade it properly. Unfortunately, with a lot of software, it can't just be upgraded and have it use all the former stuff or upgrade that along with it and just be able to work with it all as if you only need to replace one thing, like say, if you were to upgrade your web browser.

Thank for your detail explanation. :)

Why can't they just come up with a one click easy installation file.

Originally posted by certify
Thank for your detail explanation. :)

Why can't they just come up with a one click easy installation file.

Because you're smarter than that, that's why! Seriously. You'll figure it out and all you need to do, is learn -- you can do that. It might be more difficult than a simple click and install, but if that was the case, you'd lose flexibility and control. That's why Windows is a poor choice for a web server platform. That's not a flame, it's simply a fact that you have far, far more control. The more control you have, the more control you have to use your knowledge to make a better performing or custom system. One quick example, is with Windows, if they don't have the application, you probably can't make one, since Windows source code is not open. You can make things work along side of it, but you're limited. A Unix variant, you can do away with the kernel and code you own (yeah, I know, deep waters, but still), or your own web server, or just hack away at a current one and whatnot. On Windows, if IIS is exploitable, you wait on Windows to fix it. If something is exploitable in Apache, you open up vi, hack the code and put in a temp fix, for example -- if you know how. That's what a lot of it comes down to. If you know how, you know why it's better and you don't mind it not being click-install. Trust me, it's far better and the more you do and learn, the more you'll appreciate it. I'd be worried installing something, especially something so vital, if I didn't have any options or choices. After all, Apache is pretty simple to compile a default install if you don't know what you're doing or just want it to be stripped down, and it'll be pretty secure too. The more you know, the better it is though. You can't say that for other platforms or software.

Tim,

An awfully impressive post and very educational

Thanks for that

Cheers
Balaji

Originally posted by certify
Thank for your detail explanation. :)

Why can't they just come up with a one click easy installation file.

They did (well sort of) it's called Apache Toolbox. I prefer doing it myself because of the reasons Tim mentioned.

Check it out here if you are interested:

http://apachetoolbox.com/

You know, I completely forgot about that and that is good advice. Although it's not all just one-click install, it is pretty cool. Yeah, check that out. It has a menu where you can choose what you want, etc. Remember that it will still wipe out what you have now, or rather, replace it, though. I.e., if you use some module not listed or isn't an option, you'll still have to add it. Further, although it's a neat idea and can work, it isn't perfect and you should be prepared to get in there and do what you would otherwise have to perhaps do manually. However, at the same time, depending, you might be very happy with what it offers by using a configuration you choose with a limited number of components. It's something to check out anyway, even if you don't end up using it. Good luck.

If you're running a Real Operating System, you could use the portupgrade utility.

Just so you know, a lot of the things in apachetoolbox are really outdated. Tomcat being one of them.

I recommend just starting out with a HOW-TO. You can find a lot of them all over the web. Just search for something like "apache+mod_ssl+mod_frontpage".

Save your config options in a text file. Once you've done it once, it's pretty easy to upgrade the source of one of the subsystems and recompile.

Originally posted by bitserve
Just so you know, a lot of the things in apachetoolbox are really outdated. Tomcat being one of them.

I recommend just starting out with a HOW-TO. You can find a lot of them all over the web. Just search for something like "apache+mod_ssl+mod_frontpage".

Save your config options in a text file. Once you've done it once, it's pretty easy to upgrade the source of one of the subsystems and recompile.

I agree some of the packages do look outdated but isnt possible to get the newer sources and just use them? I have never used Apache Toolbox but from what I have read it only downloads the sources that are not already available on the machine, I could be wrong though. I would still recommend the manual way, it's a good thing to learn and it's not really all that bad..

Originally posted by DigitalXWeb


I agree some of the packages do look outdated but isnt possible to get the newer sources and just use them? I have never used Apache Toolbox but from what I have read it only downloads the sources that are not already available on the machine, I could be wrong though. I would still recommend the manual way, it's a good thing to learn and it's not really all that bad..

I think it's mainly the issue of some modules, etc. that won't work with the newer versions of some of the software. For example, the biggest one I know of, is the issue of newer releases of Apache and the Frontpage module. And, there's a lot of things that need to specifically check certain things in Apache, and some need time to check and make sure it will all work with the new Apache server code. Often, things will, but some things fail and cause a lot of hassles. I just depends on what you choose too, but if this guy puts some of this together as a package, he might not be up-to-date. I don't recall it downloading the components, or if it did, it might have looked for a specific version of the module in question, rather than trying to download the newest one -- and then where does it try and download them from, is another question.

Originally posted by certify
Thank for your detail explanation. :)

Why can't they just come up with a one click easy installation file.

I think that process is called Windowz.