HN2new | past | comments | ask | show | jobs | submitlogin

Why? I mean, for a very basic setup, you just run 'capify .', and then change some passwords, and you're good to go. It doesn't even really take any configuring.

Here's the thing: good engineering means that you should automate as much as possible. That way, everything is consitant. One command deployment is amazing, regardless of your technology stack.



It's more complicated than just scp'ing files over. That's all I have to say. It's fine to say that it's also better engineering, but that doesn't address the original article. Ruby is also a better engineered language than PHP in a lot of ways.


Ruby is also a better engineered language than PHP in a lot of ways.

I would say better designed, but the engineering definitely leaves a lot to be desired. Here's hoping Rubinius gets finished one day.


Well, there's also JRuby, and YARV is a lot better than MRI, although the libraries haven't quite caught up yet.


Ruby wasn't even a semi-mainstream competitor for web development until Ruby on Rails came along, so even comparing it to PHP (or worse, thinking Ruby and RoR is the same thing) is where a lot of the confusion starts.


yeah, for most simple apps, scp will do the trick, but anytime you start writing scripts to upload the same set of files on 5 different machines, it's time to use capistrano.


'cap deploy' is easier than 'scp here there'.


   [9:28pm:/playbook] DIVISION:tqbf [0:279]% cap deploy
   the task `deploy' does not exist


Really? I'm pretty new to Capistrano, but 'deploy' was just kind of built in or something. That's very strange.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: