You gotta love user written instructions – especially when they are down right wrong and you know it and the person writing it has to know it (since he has enough intelligence to actually create a blog and use it) but it is still put out there for the universe to see. This is even more bizarre when the instructions that come with the software is pretty explicit and correct. Hell I am also guilty of it.
Case in point: Getting Apache2 and PHP4 working together. I generally ignore the given instructions – my experience up until this point is that they are pretty terse and work on their systems and their systems alone. The best way is to ask google and see what the masses think. Well the masses think that this is a good set of instructions. Well they are right, up until the part where they install PHP and then it goes horribly wrong.
Why would you want to copy everything into a directory of another item and then start to copy various files all over the place – makes upgrading a painful experience: I know this as in a previous life a colleague wrote some software using a 3rd party source library – an expensive one at that. I came to work on it and was wondering why we were still using the several year old version despite the fact that everyone got the update messages forwarded to them from the library authors. What about the 30% speed increases that one of the mails raved about, what about the vulnerability that was fixed? Well they went out of the window when the muppet who wrote it took the decision not to bother with fixing the problem with his configuration and make the code fit the configuration. After that it was all down hill from there.
Anyway I eventually decided that the internet is full of muppets and read the actually instructions shipped with PHP. My god – they have instructions for getting it working on webservers I have never heard of and it is all very clear and well written, if a little terse.
So I now have a working installation of Apache2.0 and PHP4.4!