Just for the record, looks like what happened is that in spite of my assigning :mongrel_conf, nothing I did to my mongrel_cluster.yml would change its settings.
Reason was because of what I had in my script/spin file: /path/current/script/process/spawner -p 8000 -i 2 >From what I understand, it should have instead used something like this: /usr/bin/mongrel_rails cluster::start -C /path/current/config/ mongrel_cluster.yml On Jan 12, 3:14 pm, me <[EMAIL PROTECTED]> wrote: > I don't have anything associated with :mongrel_conf. > Is there a default value? > > On Jan 11, 10:38 pm, James Downs <[EMAIL PROTECTED]> wrote: > > > On Jan 11, 2008, at 2:19 PM, me wrote: > > > >> 3. It's on your app servers? > > > > yes. Local and remote (where it's deployed). > > > What's the value of :mongrel_conf in your config/deploy.rb and config/ > > deploy/production.rb files? > > > -j --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
