I’ve migrated to a new host: BlueHost. I left 1&1 after some careful consideration that boiled down to the following:
- 1&1 is running Apache 1, which is no longer supported, and doesn’t play nice with modern software. Most notably, you have to hack Gallery 3 to work with it, and mod_deflate is only available on shared hosting platforms through the official release for Apache 2. (mod_deflate gzips your files before they get sent to the browser, dramatically speeding up download times.)
- 1&1 doesn’t have a lot of utilities installed for you, such as ImageMagick, meaning that you have to install them yourself.
- The support is terrible. In almost all of my support calls, the support staff didn’t know much of anything about the way shared hosting was set up, so support calls were long and frustrating. During one call, the support analyst was about to overwrite an .htaccess file for a production site without my consent, despite the fact that the phone call was about the development environment.
- The undocumented zombie-process-killer application they have running on their servers. Despite having the script timeout set to unlimited, any script that runs for longer than 60 seconds will eventually get unceremoniously killed by a zombie-process-killer application that they have running on their serves, which is not documented anywhere. Not only is it not documented, the support staff don’t know about it, because an hour plus long conversation with a support analyst about my long-running script dying on me without a word of explanation yielded a bunch of unhelpful suggestions about logging my own PHP errors (as if that would catch the contents of an HTTP 500).
I’ve been pretty happy with the service so far. BlueHost uses cPanel for administration, which is standardized, so it’s familiar to anyone who has used cPanel on other hosting installations before. The prices are significantly better, also. We were paying $11.99 / month over at 1&1, and we are now paying $6.95 / month for BlueHost. 1&1 gave us three free domain registrations per year, whereas BlueHost only gives us one, but the extra domain is still only $10 / year – so we are saving $50.48 overall. Plus, BlueHost gives you unlimited storage space and bandwidth, and we were limited to 250 GB on 1&1 (not like we were using that much space anyway, though).
My one major complaint with BlueHost is actually a criticism of cPanel, as far as I can tell. When you sign up, the first domain you assign to your account is the primary domain, and all of the files for the primary domain are located in /public_html. The problem is that you can’t change this path for the primary domain. All additional domains and subdomains have their files put in /public_html/somefolder, which means that you can access those sites by going to http://www.primarydomain.com/somefolder, and you can’t keep your domains siloed. For sites that I create myself, I prefer to keep all of my controllers, views, models, and functions outside of the web-accessible path – the web-accessible path has an index.php that calls controllers (using mod_rewrite), and other than that, it contains images, PDFs, CSS files, JS files, and other non-PHP content. Isolating your PHP files in a non-web accessible directory in cPanel seems to be possible, but an absolute pain to maintain. Additionally, when you register a second domain (in this case, http://www.kelseyandkevin.com), it automatically creates a subdomain on your primary domain (in this case, kelseyandkevin.kevinfodness.com) which you can’t delete. It does this “for your convenience,” but it would be significantly more convenient if I had a choice as to whether this subdomain was created or not. 1&1 did not have this problem – it let you put your files wherever you wanted, and let you set specific directories for your sites.
I don’t have any problem with being forced to put all of my web content in public_html, but I would certainly like to be able to set my primary domain to pull its files from a subdirectory of public_html, and I would certainly like to be able to control what subdomains exist on my account for all of my domains, and be able to delete them at will.
I saw a suggestion on one of my searches about creating a ‘www’ subdomain for the primary domain, and redirecting content from domain.com (minus the www) to the www domain, which I will explore. However, that’s kind of a ‘hacky’ solution, because I would have to write a redirect for the non-www domain, and I would also have to write redirects for the subdomains I don’t want. Grumble, grumble.
Anyhow, I’ve implemented GZIP compression, cache control, and some other useful things that I got from Google’s Page Speed Firebug plugin to speed up the display of both kevinfodness.com and kelseyandkevin.com. I’ll be adding more performance enhancements in the coming weeks also.
In other news, I will be working on my department’s website this semester, and implementing performance enhancements, accessibility features (following the WCAG 2.0), and updating content. I’ll be blogging about my experiences working on that project, particularly the accessibility stuff, in the coming months.