Linode So Far

I’ve been using Linode now for a few months, and I basically could not be more pleased with the service. Linode recently moved to newer and faster CPUs, as well as moving over to 100% SSDs. I never thought my Linode was slow before, but it certainly seems faster now. I’ve not run any benchmarks myself, but there are those that have, and the improvements are not small. It’s just been rock solid thus far.

I moved some old websites running Perl code over to the new Linode instance. To my surprise, I rediscovered that this code is about 10 years old. I’m amazed it still works. And that’s the beauty of my Linode, or more specifically, Debian running on my Linode. I simply installed Perl and a handful of perlmods, and the sites sprang back to life. I don’t ever remember Linux being this easy to use.

And so I have nothing but great things to say about Linode. While there have been a few outages I’m not pleased with, Linode posted regular status updates and was honest about what was happening. Otherwise, response times are down by 25% over the Mac mini server I moved from … and immensely fasterĀ for the sites I moved from DreamHost.

If you’re looking for a VPS, Linode should be your final stop!

Switching to Linode

After testing out Linode for the past week, I took some time this evening to migrate the bulk of my sites to my linode (what Linode calls their VPS instances). Using Linode this past week has been amazingly painless. Their management portal, while basic in appearance, has been adequately powerful for my needs. Creating an VPS instance, a linode, is super easy. Best of all is their help section, dubbed the Library. I was able to follow the basic steps to set up my linode with a new user account, locked it down, set up LAMP and had my first website up and running within probably 15 – 30 minutes of signup up.

So, over the next few days (or maybe weeks), I’ll try and detail:

  • how easy Linode is to use, and why you should (perhaps) use it too
  • how I set up Apache to handle multiple sites using HTTPS via SNI
  • setting up SFTP for other users, but only allow them to access their website documents
  • anything I come across along the way