No not the site, but the move!
Renegade Music will be in the cloud from now on.
Or until the price actually kills me… :/
I followed Paul Normans guide with some minor problems, mainly I couldn’t move the Database to a separate EBS volume, every time I did mysql failed to start back up so … I’ll work on it.
So yea… oh and we’re doing wildcard dns now too so I don’t have to add a dns entry for, lets say, downloads.renegademusic.net I just have to add a vhost for it in my apache config and reload apache and I’m golden.
So, I’ve decided to do a little test. I’m going to move Renegade Music from Dreamhost to my own cloud based server hosted on Amazon’s Web Services platform.
The reason I’m testing out AWS is because of a recent security breach on my Dreamhost account (it more than likely was my own fault…). But I also wanted to move away from shared hosting for quiet some time.
So what does that mean overall? Nothing. Everything will pretty much stay the same for users, it’s just that I’ll have to manage everything from DNS to the nitty gritty of keeping the server instance up and running.
But it’ll also pose me with a little technical advantage too, I’ll be keeping everything on the Amazon network and I’ll be able to set up a content delivery network (cdn for short) to deliver things from cached pages and images to css for faster load times.
“As much as people are advocating piracy nowadays, do yourselves a favor: There’s a lot of music, movies, games, and software out there that’s definitely worth the money. Buy your stuff.”
I posted that on Facebook recently, and a shortened version of it on Twitter, and I stand by it. Right now,…
Music Piracy circa 1950