I'm planning to move away from Heroku too, partly because of the routing system issues you mention in your article, but also because I want to sharpen my sysadmin fu. Have you considered <a href="https://www.cloud66.com/" rel="nofollow">https://www.cloud66.com/</a> because it seems like a nice tradeoff between going "bare metal all the way" and Heroku's comfy environment.
So how does this resolve the Heroku routing problem for you? You have one server that internally routes efficiently - but what happens when you scale past one server?<p>If you're not scaling past one server, why does Heroku's routing cause you issues?
Interesting article I think (as someone who already uses Chef).<p>That said like I commented on your post, create a proper user instead of running as root, really.
Every time I see someone doing something cool with Chef, I think of this: <a href="http://progopedia.com/language/chef/" rel="nofollow">http://progopedia.com/language/chef/</a><p>And then I think, "Wow. This person must be a mad genius."
This was a very helpful and practical tutorial. I don't know why sysops is a source of perpetual confusion for me but it's good to have as many examples as possible. Could you elaborate on the actual hoops that creating a non-root user was creating for you?
With <a href="https://github.com/rmoriz/knife-digital_ocean" rel="nofollow">https://github.com/rmoriz/knife-digital_ocean</a> you can launch and bootstrap an instance using knife in a single command.<p>Works with knife-solo and traditional chef-server environments.
This is great. Two weekends ago I did the same type of migration using Linode and Capistrano. Heroku taught us what we should expect from a platform, and it seems like, as a community, we're moving towards getting those great features ourselves.
This is great. Thanks for sharing. I've been toying around with mina, but I may give Capistrano another shot. Right now I have a bunch of build scripts that would be much better suited for Chef and your setup closely mirrors my own.
I would be very leery of hosting any serious business on Digital Ocean. Their terms of service are simply too strict.<p>For example, you can't send email to your users without double opt-in.<p>Yikes!<p>Not to mention the ambiguous language banning 'offensive' and 'inappropriate' content.
Did the same thing 2 days ago! And cannot stress enough how rewarding the experience was. Although I never heard of Digital Ocean so I chose linode, but I'm also very happy with them so far.
I hate the term cloud computing and all the stupid hype that comes with it.<p>It's called mainframe computing, the exact same clusterfuck your grandfather used in 1970. With bigger hard drives.