This post, however, is not about the adventures of a Puerto Rican being thousands of miles from home (although it could certainly make for an interesting story for another day). This post is about me pulling the trigger on something I’ve wanted to do for a long time – switch my VPS (which is where this very blog is running) from Slicehost to Linode.

To begin, I wanted to state that Slicehost is very, very awesome. I’ve been a customer of theirs for more than two years, and never had any major issues with them. With the exception of some outages, their service ran smoothly for the most part. This is more than anyone can ask for. So, if Slicehost is so awesome, why didn’t I marry them? I was perfectly content in staying with them.

However, as I was experimenting more and more with Ruby, Rails, Python and other languages / frameworks, my VPS – which was the smallest slice available at 256 MB – was obviously starting to suffer under the memory constraints. Since these were mostly experiments, I didn’t want to splurge and pay almost double for a 512 MB slice. That’s when Linode announced that they would be increasing the RAM sizes of all their slices. So it was either to stay with Slicehost and have my VPS struggle to keep up with my experiments (or pay more per month), or switch VPS providers. After reading all around the Internet about how good Linode was, I decided to go for it.

I opened an account with Linode and instantly had my sparkling new VPS running. I transferred all my files from the old Slicehost VPS and just had to point my domain names to the new Linode VPS. My main concern initially was that Slicehost had really spoiled me with their control panel, especially for DNS management. It was what had initially drawn me into their service to begin with, so leaving that behind was a bit scary. Thankfully, Linode has their own control panel that’s equally great to use. I was able to configure and point my domain names to the Linode VPS, and had everything working quickly.

As far as performance, I had been reading for years how Linode has faster I/O performance than Slicehost. Turns out that those tests seem to be true – The VPS as a whole feels much snappier, from logging in via SSH to serving up this very blog.

One of the major issues people had against Linode in the past was that they lacked any integrated backup system, a la Slicehost. They actually introduced backups a few months ago. This wasn’t a major concern for me (I’m using Tarsnap, which deserves a blog post of its own), but for those who need this sort of service, know that they have you covered.

Like I mentioned, Slicehost is great, and I wouldn’t encourage people to not use their services. I just had different needs that Linode seems to be handling as well as I expected. It’s only been a couple of days, but I think I’ll be shutting down my Slicehost VPS for good.

It might sound like just another online file storage site, but it really is not. It’s ridiculously easy to use. Once you install their client software and create an account with them, your computer will have a special folder, where you can just drop files in and they will automatically be synced on your account. No need to do any manual syncing or waiting for a timed sync to occur. It’ll happen totally transparent from your regular workflow. Provided you have a fast Internet connection, the synchronization process is virtually instantaneous. Then you can either grab the files from a web interface, or by installing and configuring the client in another computer. It’s that damn easy. Take a look at the tour they have on their site.

I must admit, I was a bit skeptical about this service after I read about it in TechCrunch earlier this year. I thought it wouldn’t be anything special compared to any other site that provides similar services. However, after reading more and more about it, the curiosity got the best of me. I scrounged for an invite and eventually got one. I signed up, but to be honest I never used it much. I only have access to Mac and Linux computers at the moment, and Dropbox was Windows and Mac only, so I was rather limited as to where I could use it.

However, the excitement arrived yesterday, when not only I read that Dropbox launched publicly, but they also released a Linux version of their client software! I immediately downloaded the client at work (laptop using Ubuntu 8.04), created my account. and it worked just as it did on the Mac. I started transferring files and got them when I arrived home. Everything went without a hitch. I’m now finding more and more uses for Dropbox, particularly work-related files that I can access at home.

Kudos to the entire Dropbox team for putting out some quality work.

Thankfully, people in the Rails community have been working on different solutions to handle this. One I discovered recently, which I’m really loving a lot, is Hoptoad, brought to you by the awesome people over at thoughtbot. Really, how can you not be an awesome group when your blog is titled Giant Robots Smashing Into Other Giant Robots?

Anyway, Hoptoad is a service which captures all exceptions that occur in your Rails application, and aggregates them into one place. This way, if you have, for example, a link to AJAX functionality that causes a 500 error, you’ll only get one E-Mail notifying you about the error. The service will actually log the times it’s happened, though. It also provides a full stack trace, session information, parameters that were passed, and just about everything else you need to make a full assessment on why your application failed. Oh, and one more important thing: it’s totally free. Can’t beat the price.

It’s as simple as creating a new account and setting up a project, installing their plugin on your application, putting the assigned API key in an initializer file, and that’s it! It took me about 2 minutes to set everything up the first time. The interface is pretty straight-forward. When you first log in, it will show if any of your projects has any errors (which any developer can mark as ‘Resolved’ so it won’t show again). If there are (and face it, we all get errors at one point or another), then as I mentioned previously, you can view the stack trace to see what happened. Nice, simple and helpful.

I’ve noticed there are some other sites that offer these services (like Exceptional), but none that seem to have the simplicity of Hoptoad. Not that I think the other services are bad, but it’s just not what I want at this moment. In my particular case, I really don’t need to have an app that integrates with other services, let’s me leave comments about an error, or see how many times in the past week the error occurred. I just want to know if my app is getting errors. Hoptoad does just that.

I fully recommend Hoptoad for any Rails app. If you don’t have any sort of exception notifier in your app, you should get something now. If you do, then I hope you never have to constantly use it!