I’ve had a slice at SliceHost for longer than I care to admit by now1, I just hadn’t quite gotten around to ever testing and configuring it the way I wanted to.
Well, I finally got around to wiping out whatever I’d been playing with there before and dumping on their stock Debian 4.0 image. After running through their tutorials on setting up Apache2 and PHP, I was good to go.
The base system with my webserver and database running read at about 25 MB of used RAM. Not bad for a fully functional, if barebones, webserver. I’d been worried that, coming from a fully dedicated box with 1 GB of RAM, I would run into a memory bottleneck, but fortunately that didn’t seem it would be a problem.
The next important step was to do some testing. I played around with MySQL, running some basic queries, just to see if it was noticeably laggy after a casual poking. Again, everything looked fine.
The next, and really final, step was to dump a copy of my blog on the slice and see how it ran. After some complaining about the default max_upload_size value in PHP, I got a copy of my database imported using phpMyAdmin and a quick scp -r later and I had an exact copy of my blog setup and ready to go.
All-in-all, it looks like performance is at the very least on-par with the other hosting I’ve used in the past. The performance over DreamHost, where my blog has lived for several months while I really decided where to host it, represents about a 10% improvement3.
I’m still not ready to make the DNS switch, but at least I’ve realized I’m being too paranoid about the memory limits. In the end, the only other reason to stay with my expensive dedicated server is the convenience of Plesk, which scratches my lazy itch perfectly.
If I can get a few scripts hobbled together (in one language or another) to help automate things like vhost and database creation, I may be able to do away with Plesk entirely.
One final problem, and one I’m looking for opinions on, is what to do about email. I’m not planning on dumping DreamHost any time soon4, but I would like to move my email along with my blog if possible.
So who do you use for email? Any problems? Only condition is that they have to offer IMAP…
Missing an Email? It may be Media Temple’s Fault
It started last week when I was trying to sign up for Ron Paul Christmas. For some peculiar reason, I didn’t receive the welcome email. After talking with the site owner, it turned out (mt) was rejecting the email because the email address wordpress@ronpaulchristmas.com didn’t exist on the sending server.
Now, this isn’t particularly unusual. There is no requirement1 that an email address actually exist for a server to send email as if it were from that address. This is especially true from Wordpress blogs, which often send email from
wordpress@domain.comaccounts on behalf of their owners. Now, since this is only used for outgoing email, in most cases users would never bother setting the email account up. Why would you? You’re never going to be receiving email there2, so what’s the point?Well, (mt) apparently knows better than you do… For “security reasons”3, their grid service does a “callback” check on every incoming email address. If the server handling mail for
domain.comdoesn’t recognize that account (such as ourwordpress@domain.comexample), (mt)’s server will reject the message.I’ve tried to point out that this kind of behavior can be detrimental, particularly in the age of blogging and web services we now exist in, but the best answer I’ve been able to get out of (mt) is that I should add the sending address to their Mail Protect whitelist. Well great, unless I can add
*@*to the whitelist, or at the very leastwordpress@*, that’s hardly a viable solution - how do I know the address that’s sending to me if I never get the email?If you use Media Temple’s grid service4, please contact (mt) immediately and tell them this is an unacceptable situation. I love a lot of aspects of their grid service, but this is clearly not one of them…