So, Python isn't really a CMS topic unless you're a Plone user. However, as my world at work slowly moves from Python to Java as the language of choice...I'll promote this underdog open source language anytime. From the IBM developerWorks site:
"It can happen anywhere, at any time. You’re doing your job, minding your own business, and it suddenly dawns on you: you’re the company’s webmaster."
--Shane Schick, "Accidental webmasters rejoice – help is on the way", GlobeandMail.com, September 5, 2007
A few months ago I mentioned that I was hosting my site using a "budget shared hosting plan through my reseller site which is comparable to the hosting plans offered by GoDaddy". In that same article, I also mentioned that although I prefer to run my sites on a Virtual Private/Dedicated Server (VPS/VDS), I wanted to try experimenting with the cheap shared hosting plans despite the plans not offering full MySQL functions such as CREATE TEMPORARY TABLE. For the most part, my sites have been running fine on the shared hosting plans but I wanted better control (oh how I miss Linux command line via secure shell). So, I began searching for a better reseller hosting plan. Unfortunately, my search for the perfect reseller host plan still continues.
I thought my hosting requirements were pretty simple. I wanted a reseller hosting plan that provided CPanel, PHP5, MySQL5, secure shell, and a license to a client billing system such as ClientExec. Oh and I wanted to be sure the hosting plans provided were Drupal friendly. While I host more than just Drupal sites I've found that if the server is configured properly to run Drupal then it can run almost any other PHP-based CMS out there. All in all I wanted a shared hosting plan where I spent less time managing the server, yet had the controls I needed via a Linux shell. Simple enough right? In fact I thought I found a great reseller plan through ResellerZoom (RZ). However, after spending most of my weekend hours trying to work it all out, I've come to the conclusion I'm still looking for something that works better.
If the project leaders and users of your favorite content management system are still debating when they should drop PHP 4 support, it looks like the PHP development team has helped make that decision for them. PHP.net just announced the End of Life for PHP 4. Starting in 2008, only security updates on a case-by-case basis will be provided...and PHP 4 is dead in August 2008.
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.