Just in case someone is very bored today: http://pastie.caboo.se/58616
On May 3, 6:30 pm, August Lilleaas <[EMAIL PROTECTED]> wrote: > For some reason, using mongrel didn't even cross my mind. Trying that > now. Managed to get mongler running on localhost:4000, all I need to > figure out now is how to proxy it properly =) At the moment I'm > getting 403 forbidden when doing ProxyPass /http://localhost:4000, > not sure why that is. Going localhost/images/rails.png is working, so > I guess I did something right. > > Thanks! > > On May 3, 5:47 pm, "Brian Hogan" <[EMAIL PROTECTED]> wrote: > > > Pretty much what I use, almost exactly. Would love to update my original > > documentation, but there's this book that's supposed to be coming out that > > contains the updates. > > > I was just asked to present 2 days ago so please, no heckling. I'm nervous > > enough as it is. > > > :) > > > On 5/3/07, jrimmer <[EMAIL PROTECTED]> wrote: > > > > I'll be attending your session, Brian, but primarily just to heckle > > > and correct you. I should be easy to spot as I'll be the incredibly > > > intelligent guy that impressed you so much. > > > Or... uh... something like that. Thanks for your original > > > documentation on deploying Rails on Windows, it was VERY helpful! > > > > As for the lack of Mongrel 'clustering' support... I wish the name > > > would change as 'cluster' is far too overloaded a term, I prefer > > > 'packs'. It's simply an issue of process management so a few batch > > > files will do the trick. I have four batch files for the > > > installation, removal, starting, and stopping of a Mongrel pack. > > > Their contents are as follows: > > > > # > > > # mongrel_install.bat > > > # > > > @echo off > > > call mongrel_rails service::install -N <app name>-9000 -c <app path> - > > > p 9000 -e production > > > call mongrel_rails service::install -N <app name>-9001 -c <app path> - > > > p 9001 -e production > > > ... > > > call mongrel_rails service::install -N <app name>-9016 -c <app path> - > > > p 9016 -e production > > > > sc config <app name>-9000 start= auto > > > sc config <app name>-9001 start= auto > > > ... > > > sc config <app name>-9016 start= auto > > > > # > > > # mongrel_remove.bat > > > # > > > @echo off > > > call mongrel_rails service::remove -N <app name>-9000 > > > call mongrel_rails service::remove -N <app name>-9001 > > > ... > > > call mongrel_rails service::remove -N <app name>-9016 > > > > # > > > # mongrel_start.bat > > > # > > > @echo off > > > net start <app name>-9000 > > > net start <app name>-9001 > > > ... > > > net start <app name>-9016 > > > > # > > > # mongrel_stop.bat > > > # > > > @echo off > > > net stop <app name>-9000 > > > net stop <app name>-9001 > > > ... > > > net stop <app name>-9016 > > > > On May 3, 10:38 am, "Brian Hogan" <[EMAIL PROTECTED]> wrote: > > > > +1. > > > > Mongrel can install as a service on Windows. There is no clustering > > > support > > > > for Mongrel on Windows (though I hear it's coming...) and so you just > > > > install mongrel as a service once for each port. You can then use the > > > > mod_proxy_balance approach in Apache 2.2. > > > > > I'll be talking about deployment on Windows at RailsConf apparently, so > > > come > > > > see me if you're going :) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
