Conversely, PHP has one several advantages over Rails. Most notably, immediacy. Deployment via SCP is very satisfying.
Though not as satisfying as using source control and having a one command "deploy" that's just as quick as SCPing a bunch of files.. I can deploy - to production - local builds of my Ruby projects in seconds.
There are no significant advantages to using PHP or disadvantages to using Ruby or Rails presented in that blog post, even though it tries to make it seem that way. (And on the library complaint, the Ruby libraries that came along for things like S3 and EC2 are better than the official ones by a long shot.)
Despite that, different strokes for different folks. Use what works for you and all that!
I come off like a Capistrano fanboy in this thread, but I guess that I kind of am.
I only ever used the SCP method when I did PHP stuff, but the projects were never anything that big. Now that I do Rails all the time, having a tool like Capistrano is amazing. 'cap deploy' copies my code, changes the symlink, updates my database schema, notifies my error reporting, restarts my webserver, and cooks me dinner.
Okay, I exaggerate. But seriously. Automation! It's awesome.
It is! And even if you just jury rig it! Several of my projects have a deploy script that's just a bash one liner that does a git push and does a git pull and touches a restart file on the server :-)
Though not as satisfying as using source control and having a one command "deploy" that's just as quick as SCPing a bunch of files.. I can deploy - to production - local builds of my Ruby projects in seconds.
There are no significant advantages to using PHP or disadvantages to using Ruby or Rails presented in that blog post, even though it tries to make it seem that way. (And on the library complaint, the Ruby libraries that came along for things like S3 and EC2 are better than the official ones by a long shot.)
Despite that, different strokes for different folks. Use what works for you and all that!