So I finally moved vps providers over to https://www.arpnetworks.com/, I will still continue to use my prgmr account but, bandwidth issues were the only limitation there. The service has been awesome and I have yet to have an issue. They are a kvm based host so if you need real para-virt, I would check out prgmr, linode, ec2 etc. If you need anything else, I would head over there.

So a while ago I spent a good deal of time dealing with deployinator from etsy. It was an awesome experience which lead the team I worked at Rackspace to dreadnot. We came up with this idea as deployinator didn't fit our needs, but, at this point, wasn't a failure. While it maintained continuous release techniques unheard of for most corporations, it still maintained integrity that most companies lack. We (at rackspace) only lacked a few things from it but that was enough to not turn us away but develop our own rolling release sweet with an integrated chef deployment integration. I had a lot of time to adjust, reinvent, patch and maintain our internal deployinator release up until we switched over to dreadnot. This was not an easy decision as we had many things to overcome.

Some of the things I committed was multi protocol support such as git@ (ssh) vs. https:// that github supports, my next goal was to integrate bitbucket as well. Some personal interest would be to revamp this with other developers to add more features for rolling releases and to push this to the community as an excellent example of workmanship. Until then, check both the projects out and have some fun playing with them.

New site is coming along, had to do a lot of work on my django backend to get this going again, been a while.