Comments on: F. How To Deploy your first rails app to Dreamhost using Capistrano in Windows http://firstruby.wordpress.com Master ruby with us Thu, 17 Dec 2009 09:45:28 +0000 http://wordpress.com/ hourly 1 By: Ed Ruder http://firstruby.wordpress.com/6-how-to-deploy-your-first-rails-app-to-dreamhost-using-capistrano-in-windows/#comment-7 Ed Ruder Fri, 12 Jan 2007 09:25:27 +0000 http://firstruby.wordpress.com/6-how-to-deploy-your-first-rails-app-to-dreamhost-using-capistrano-in-windows/#comment-7 Oops, that should have read: - A few suggestions: and - The multi-line [code] blocks are rendering to a single line... Oops, that should have read:

- A few suggestions:

and

- The multi-line blocks are rendering to a single line…

]]> By: Ed Ruder http://firstruby.wordpress.com/6-how-to-deploy-your-first-rails-app-to-dreamhost-using-capistrano-in-windows/#comment-6 Ed Ruder Fri, 12 Jan 2007 09:22:58 +0000 http://firstruby.wordpress.com/6-how-to-deploy-your-first-rails-app-to-dreamhost-using-capistrano-in-windows/#comment-6 Thanks, your guide helped me out! I hadn't seen the "set :user" line elsewhere--it fixed my "cap deploy" from a Windows machine. (I don't know why the "cap deploy" succeeded from a Mac OS X box without the "set :user" line.) A couple of suggestions: - The multi-line <code> blocks are rendering to a single line, off the right edge of the screen (on FireFox 2.0 on Windows). - The after_deploy and after_rollback methods contain hard-coded paths that are unnecessary--I changed them to "run touch #{deploy_to}/current/public/dispatch.fcgi", which seemed to work well. - The error you highlight, "couldn't find any processes matching...dispatch.fcgi", isn't necessarily an error if your app isn't running yet. I don't recall where I read that, but it does appear to be innocuous (always?). Thanks, your guide helped me out! I hadn’t seen the “set :user” line elsewhere–it fixed my “cap deploy” from a Windows machine. (I don’t know why the “cap deploy” succeeded from a Mac OS X box without the “set :user” line.)

A couple of suggestions:

- The multi-line blocks are rendering to a single line, off the right edge of the screen (on FireFox 2.0 on Windows).

- The after_deploy and after_rollback methods contain hard-coded paths that are unnecessary--I changed them to "run touch #{deploy_to}/current/public/dispatch.fcgi", which seemed to work well.

- The error you highlight, "couldn't find any processes matching...dispatch.fcgi", isn't necessarily an error if your app isn't running yet. I don't recall where I read that, but it does appear to be innocuous (always?).

]]>