After my old web host made me really mad the other month I decided to grab a load of virtual servers and be my own web host (hosting client sites, projects etc.)
So now I have DNS, database/web servers etc. all under my control on shares that I can chop/change at will.
It's turned out to be phenomenally cheaper! Than having 1 dedicated server and a shard hosting package.
I'd be very interested in seeing a blog post detailing that. That would be very useful for hosting client projects. I'm working on a project that aims to be similar to Heroku but runnable on a handful of virtual servers from any VPS service.
>Imagine having a directory full of Ruby web apps, e.g. ~/Sites. To deploy an app, just drop your application’s directory into ~/Sites. To undeploy it, remove the application’s directory. The application directory’s name is used as the domain name. No manually signaling the web server for a restart.
While that sounds very useful, what I'm working on is more along the lines of Heroku's distributed dyno model. In their terminology, a dyno is a Thin web application server process. When an app needs to be started up, it will be possible to determine how many dynos are needed, and they will be automatically started up across the grid of virtual servers and balanced using a custom load balancer.
After my old web host made me really mad the other month I decided to grab a load of virtual servers and be my own web host (hosting client sites, projects etc.)
So now I have DNS, database/web servers etc. all under my control on shares that I can chop/change at will.
It's turned out to be phenomenally cheaper! Than having 1 dedicated server and a shard hosting package.