So I see a lot of guides like this (I have one myself), but none that are built on top of Chef-solo/Ansible/Knife.<p>Which makes me wonder, which is the correct way which <i>lends itself to automation </i> and doesn't depend on AWS/AMI?
Choose OpenBSD for your Unix needs. OpenBSD -- the world's simplest and most secure Unix-like OS. The world's most used SSH implementation OpenSSH, the world's most elegant firewall PF, the world's most elegant mail server OpenSMTPD. OpenBSD -- the cleanest kernel, the cleanest userland and the cleanest configuration syntax.<p>Also, <a href="http://puma.io/" rel="nofollow">http://puma.io/</a>.
I never knew about CheckInstall: a utility that tracks all the files modified during "make install" and creates a Debian package for them. That's just great! Bonus: you can then use the package it creates to install on other machines. <a href="https://help.ubuntu.com/community/CheckInstall" rel="nofollow">https://help.ubuntu.com/community/CheckInstall</a>
Rather than installing Ruby 2.1 from source using rbenv, it is also possible to install Ruby 2.1 using APT, by using the Brightbox PPA: <a href="https://launchpad.net/~brightbox/+archive/ruby-ng" rel="nofollow">https://launchpad.net/~brightbox/+archive/ruby-ng</a>
The Phusion Passenger APT packages are compatible with the Brightbox Ruby packages.
That's a great guide! We realized that a lot of people were spending a lot of time on stuff like this, and that's why we built Cloud 66. We help you to deploy and manage your applications on any cloud (ie. DigitalOcean, AWS, Rackspace etc) - feel free to check us out <a href="http://cloud66.com" rel="nofollow">http://cloud66.com</a><p>Disclaimer: I work for Cloud 66
This write up is something that I've been looking for. Some folks at the local Rails meetups have also told me about Dokku, which facilitates deployment for sure, but I'm left wondering what the ramifications/disadvantages of an automated process (like Dokku and I guess Heroku) vs a "proper" setup like this one described.
I can attest that the ruby-build project is a huge lifesaver. If you need to build an experimental ruby, it's the way to go. You can install it completely out of the system path. I really appreciate the effort that was put into it because it probably saved me about a week of work.
I find chruby (<a href="https://github.com/postmodern/chruby" rel="nofollow">https://github.com/postmodern/chruby</a>) to be a much nicer alternative to rbenv nowadays.
Bad firewalling advice imo. Use ubuntu's ufw. Admittedl, ufw feels <i>more</i> difficult if you already know iptables, but it's way more robust than the example given there.