search for: configure_mongrel_clust

...luster/recipes'' - deployment: rake deploy (fails because config file is at: /home/me/sites/myapp/current/config/mongrel_cluster.yml) ... executing "mongrel_rails cluster::restart -C /home/me/sites/myapp/config/mongrel_cluster.yml" ... then I thought I could give "cap -a configure_mongrel_cluster" a try, hoping it would put things into the right order, but I got this: ** [out :: xx.xx.xx.xx] !!! Path to log file not valid: log/mongrel.log ** [out :: xx.xx.xx.xx] cluster::configure reported an error. Use -h to get help. So what is wrong with the way I approached capistrano mon...

...d. -removed some validation rules and delegate to mongrel_rails. -added Capistrano task library. Please rerun mongrel_rails cluster::configure to ensure smooth operation. ***Capistrano Recipe*** Add to config/deploy.rb: require ''mongrel_cluster/recipes'' Example usage: cap -a configure_mongrel_cluster Variables mongrel_servers: Number of Mongrel servers to start. mongrel_port: Starting port to bind to. mongrel_address: Address to bind to. mongrel_environment: Rails environment to run as. mongrel_config: Path to config file. use_sudo: Whether or not tasks that can use sudo, ought to use sudo....

...ing the user/group of mongrel_rails process. * Added bin/mongrel_cluster_ctl to start/stop all clusters on a server. Usage: mongrel_cluster_ctl (start|stop|restart) [options] * Addred resources/mongrel_cluster * Fixed bugs in Capistrano recipes with mongrel_config variable. * Remove use_sudo from configure_mongrel_cluster task. * Changed restart_mongrel_cluster task to call stop/start. * Added Capistrano tasks to support mongrel_cluster_ctl. Known issues: * Output suppression doesn''t quite work as expected. Some messages from "mongrel_rails start" are not suppressed. * Changing user/group sh...

...ing the user/group of mongrel_rails process. * Added bin/mongrel_cluster_ctl to start/stop all clusters on a server. Usage: mongrel_cluster_ctl (start|stop|restart) [options] * Addred resources/mongrel_cluster * Fixed bugs in Capistrano recipes with mongrel_config variable. * Remove use_sudo from configure_mongrel_cluster task. * Changed restart_mongrel_cluster task to call stop/start. * Added Capistrano tasks to support mongrel_cluster_ctl. Known issues: * Output suppression doesn''t quite work as expected. Some messages from "mongrel_rails start" are not suppressed. * Changing user/group sh...

Sorry for the newbie question but I''m stumped: I have an app that requires sudo to run mongrel_rails. For my capistrano recipe is do it like this: sudo "mongrel_rails start -e production -p #{application_port} -d -c #{current_path}" Which works famously. Now I have tried several things for my restart task. Here they are: sudo "cd #{current_path} && sudo