I really do still think you're going down the wrong path running mongrel directly on 80, instead of sending it through a proxy on your web server. I think it's going to cause you headaches in the long run. Do you have any web server running on that machine? What web server? Is there any reason you are choosing not to go the route of having apache (or other specialized) web server be a front end to your mongrel?
Jonathan Kirk Haines wrote: > On Mon, Mar 31, 2008 at 2:31 PM, James Testa <[EMAIL PROTECTED]> wrote: > >> Kirk, >> Do you mean run >> >> % mongrel_rails start -d -p 80 >> >> I tried that and mongrel won't start. But mongrel will start with >> >> % mongrel_rails start -d -p 3000 >> >> Is there a mongrel configuration file somewhere that is overriding >> the port setting? >> > > Okay, if it won't start, then do you get an error? > > Odds are that either there is already something running there, or you > are starting mongrel without sufficient permissions. To bind to a port > below 1024, a process has to be running as root. > > > Kirk Haines > _______________________________________________ > Mongrel-users mailing list > Mongrel-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > -- Jonathan Rochkind Digital Services Software Engineer The Sheridan Libraries Johns Hopkins University 410.516.8886 rochkind (at) jhu.edu _______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
