I hate this about deploying Rails applications. It's always a teeny tiny little thing, but it almost always ends up with a trip through random stackoverflow answers, comments, blog posts and the occasional doc filed under 'known issues'.<p>I have _only_ 1 production application hosted on a hand-built DigitalOcean stack - hell it was a such a process I wrote a guide on how to do it, mainly for my own benefit in the future.<p><a href="http://tech.pro/tutorial/1335/devops-for-dummies-vps-configuration-from-scratch-rails-nginx-postgresql" rel="nofollow">http://tech.pro/tutorial/1335/devops-for-dummies-vps-configu...</a><p>Surprise surprise, I try to follow _my own guide_ on a new project I started and it doesn't work as expected. Either RVM changed since writing it, Ubuntu issue with locales preventing postgres from starting, or the odd issue with postgres not installing with a default user. It's a cluster<i></i><i></i>.<p>Alright, enough fiddling about. I bought myself a book to learn from a professional [0]. Surprise surprise! Outdated not 1 month after it's been released. No longer working, again hunting down the comments area. :P<p>There's a reason why Heroku is so popular: it makes deployments mind-numbingly simple. (Plus you can scale, but let's worry about that after the app actually runs!)<p>I'm going to give this a shot using a brand new Ubuntu 13.10 x64 DigitalOcean VPS with a simple CRUD rails application I have. But I'd bet my left arm that something is going to go wrong and yet again I'll have to dive deep into the recesses of the web.<p>[0] - <a href="https://leanpub.com/deploying_rails_applications" rel="nofollow">https://leanpub.com/deploying_rails_applications</a>