System Administration

During the past couple years I have recommended to people that they host their Drupal sites on a virtual private server (VPS) instead of a shared hosting plan.   While a large number of people do not have problems running Drupal under shared hosting plans, I have always felt that there are less headaches with using a VPS to host your sites.  For example, with a VPS I don't have to worry whether the shared hosting plan gives me the necessary MySQL privileges needed by Drupal (especially CREATE TEMPORARY TABLES and LOCK TABLES).  From time to time, you also hear from people with "Drupal friendly" shared hosting plans eventually find that their hosting company isn't so friendly toward their Drupal site.  Planet Drupal contributor, Clancy Ratliff, is one of the most recent  examples for having a host provider not really happy she is using Drupal.  So I often ask myself, is shared hosting for Drupal really worth the trouble?

I don't know if shared hosting is worth the trouble but a chain of events have brought me to giving shared hosting another chance for my Drupal sites.  Last month, I pushed my VPS so close to the bleeding edge that it became unstable.  While I was able to get my sites back online, the downtime clearly told me it was time to move my sites to a new server.  While most visitors observed a performance improvement  for my Drupal sites since the server migration, it's only now that I'm letting the cat out of the bag.  For the past week, CMSReport.com has been under a shared hosting plan and not a VPS.   I'm currently running my site using a budget shared hosting plan through my reseller site which is comparable to the hosting plans offered by GoDaddy.

I don't know how long I'll keep my site on a shared hosting plan but I am currently enjoying a break from the work, worry, and experimentation that comes with administration of a VPS.  While I may go back to a VPS, I thought it would benefit some newbies and other Drupal users my experiences and thoughts on migrating my sites from a VPS back to a shared hosting plan.

First, let me say thank you for everyone that stops by to reads my blog as well as seeing the latest articles I bookmark on content management systems.  You people are the greatest and this has been a very fun year for me!  Secondly, let me say you may not be able to read this post through the weekend.

I'm currently in the process of moving CMS Report and some other sites I manage to a new VPS.  The original reason for the change was to move my sites off of a legacy version of Linux (Fedora Core 2).  However, I'm also making the server change because of too much bleeding edge experimentation by yours truly that has brought my server's stability into question.  Believe it or not, a reboot of the server doesn't fix everything!

When I originally started hosting my own sites on a server (VPS/VDS), I opted for the easy way to manage those sites by using an online control panel. I originally started with Plesk but eventually moved to cPanel. cPanel at the time seemed to be the control panel everyone was talking about. However, I quickly found that although I liked cPanel it seemed to be dated by the fact that its primary web server support was for Apache 1.x. Support for Apache 2.x was promised in the next version of the control panel, cPanel 11, so I waited patiently for its arrival.

This past week saw updates for both Wordpress and Wordpress MU.  While both open source packages are blogging applications they are not quite the same software.  Wordpress MU is intended to run up to hundreds of thousands of blogs with a single install of WordPress. Hence the MU in Wordpress MU stands for Multi-User.

A security update is available in both branches of  Wordpress as 2.1.3 and 2.0.10.

Michael Kaply has been writing a series of articles on how to deploy Firefox 2 within the Enterprise. I wrote last year that one of the difficulties of deploying Firefox and Thunderbird in the enterprise was the lack of tools Mozilla provided for deploying the software. I'm happy to say that Kaply's articles do a fairly good job on providing some solutions for those organizations that need to manage a large network of clients. Kaply's original intent is to cover the following topics regarding deployment of Firefox 2 within the enterprise:

As we mentioned earlier, phpBB.com was down due to drive failures on their RAID system.  Late Sunday evening, phpBB.com not only brought their site back online, but also redesigned their site.  An announcement was posted in phpBB's forum explaining the details.

I'm in the middle of upgrading my VPS server from PHP 5.1.6 to PHP 5.2.1.  So if you don't hear from me anytime soon...you now have an explanation.

A debate that is going on among many CMS projects. Ryan Boren asks if it's time for Wordpress to drop support for MySQL 3.23?

Over the weekend, I upgraded the server that hosts CMS Report with the latest stable releases of MySQL and eAccelerator. The upgrade from MySQL 4.1 to 5.0 was easy compared to the upgrade I made a year ago from MySQL 3.23 to 4.1. This time around I also have use of CPanel which meant I could make the database upgrade with at least one eye closed. My journey with upgrading from eAccelerator 0.9.4 to 0.9.5 however took a lot longer.

I've been using eAccelerator 0.9.4 since it was released early in 2006. I've gotten into some trouble in the past by those smarter than me when I tried to explain exactly what eAccelerator does and does not do. To play it safe this time around, I'll give you the summary of what eAccelerator does straight from eAccelerator.net: