Earlier quoted context omitted.
This is their first iteration. For a simple Rails app, setting up Ubuntu an RDBMS and Redis is trivial, thats true. The point is that managing 5 Rails apps, one on Mysql, two on Postgres, two on CouchDB, one with Redis, one with Memcached... (and so on so forth) gets non-trivial soon if you don't grow beyond managing it all on your development machine.[1] Suddenly, all that trivial development stuff becomes a questio…
http://news.ycombinator.com/item?id=4135058 I just got done proselytizing the benefits of automation. I'm not arguing against myself. I'm concerned with why everything Rails people promote and celebrate seems to be along the lines of what originally popularized the framework. "Make a blog in 15 minutes!" --- you remember this one? Were you programming back then? It's exemplary of what I'm talking about. Why are they…
If you're talking about what they deploy, rather than what they're written in, neither Capistrano nor Vlad are in any way limited to deploying Ruby. Capistrano has a few minor built-in niceties for deploying Rails (basically a few pre-written tasks so you don't have to write them yourself) but it's no less applicable to deploying other projects.