Those visiting CMS Report yesterday evening into this morning likely found that they couldn't reach the site. My apologies! I run CMS Report and a few of my own sites on a virtual private server. Sometimes I just get an itch to go bleeding edge on the production server to get the adrenaline...so why not? What harm could I really do to my Drupal and Wordpress sites? Well...the hole I dug myself into was a little bit bigger to climb out then I had expected! Worse, the only site I really had to restore from backup was CMS Report!
Well at least none of my actual clients were affected by my experimentation. Plus you have to be impressed...I actually had backups ready to go. Either way, you can expect the server to run a little slow today until I get a chance to tweak things a little more...
Comments
Addicted
Glad to see that you are back up. I usually check things out at the end of my work day on the latest CMS headlines. You being down for the evening sort of ruined my routine!
Glad you're okay!
I missed you, too. Glad to hear there was no serious problems. I figured you were messing with stuff you learned from the Pro Drupal book! ;)
cPanel
No...I've been trying out some of the Edge level software from cPanel 11 and trying to upgrade from Apache 1 to Apache 2. Ran into too many problems that I'll wait until the build is more stable. Also may just start with a fresh VPS which can be purchased rather cheaply though Dakota Hosting (Disclaimer - I'm connected with Dakota Hosting).
APC installed
One of the changes I did get around to was installing the PECL Alternative PHP Cache (APC). This is a first for me as I've always used eAccelerator in the past. I'll be interested if anyone notices a speed difference to make all this tweaking worth it.
-Bryan