Today I found out my local Xampp install is pretty old since I could no longer run the beta of WordPress 3.2. It led me to the updated requirements to run WordPress on webservers. Indeed it has been changed to the minimum php version of 5.2.4 and I was running 5.2.3.

Here’s the new 3.2 beta admin interface:

It also reminded me I still need to learn more about upgrading Apache/PHP/MySQL and the works on my VPS. I’m now running version 5.2.14 which is the version that came out in July last year. It should hopefully last me about 2-3 years before the software I want to run can no longer run on it.

Now, since I’m not a LITTLE BIT sure I’m going to fuck an upgrade up but DEAD CERTAIN, I’m probably not going to attempt that until I find a way of being absolutely sure I can create a backup of the entire thing and restore it back when it’s necessary. I managed to learn how to work with iptables just enough to put basic security in, but, upgrading the entire enchilada myself on CentOS is unknown territory. Quite frankly, even though I know I must check what is capable to run together in version numbers – that’s probably the first mistake I’ll make. Like, upgrading PHP without upgrading Apache or something (and FAIL). Screw up DirectAdmin, PhpmyAdmin and whatever else is on there. You know and I know: every mistake you can possibly make will be made if I attempt this. The ultimate fate of the mad bomber: after doing everything wrong, they probably know everything there is to know in a short amount of time.

Since you’re all curious why even I feel uncertain about doing this: I’m not a linux geek. And even if you are one, maintaining webservers on it is quite a particular sport.

I will try it though; right after I check my hosts options for: “Total Retard Package: any idiot is able to restore and try again”.