Hey All, I am looking for an example of the proper config settings for background rb to run my rails app and my backgroundrb instance on separate machines (or more precisely, to have a rails cluster with one backgroundrb machine). Does anyone have such examples? Thanks! -Noah -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080309/dee389bd/attachment.html
Hi Noah, Sorry for late reply, I have been terribly busy with my day job and now catching up on mails. On Sun, 2008-03-09 at 15:31 -0700, Noah Horton wrote:> Hey All, > I am looking for an example of the proper config settings for > background rb to run my rails app and my backgroundrb instance on > separate machines (or more precisely, to have a rails cluster with one > backgroundrb machine). Does anyone have such examples? >Okay, so you need one BackgrounDRb server for each machine so as mongrel clusters running on that machine has access to BackgrounDRb server running on that machine? If yes, you can simply use "0.0.0.0" as ip, and your mongrels running on that machine will only use BackgrounDRb server running on that machine. Also, I will advise you to use MemCache cluster for storing status/result objects so as even if next request goes to mongrels running on another machine, you will have access to result objects from another BackgrounDRb server. I dunno, if I am answering your questions, but if you have doubt shoot back.
Actually, my requirements are a bit different. Sorry for being unclear. Thanks for your help on this! My setup is that I have a cluster of machines (lets call them A, B and C) that are all running clusters of mongrels (lets say 3 per machine, labeled A1, A2, A3, B1, B2, B3, C1, C2, C3). I want to setup another machine, D, such that it runs nothing but BackgroundRB. All of the mongrels on all the machines (A, B and C) would call into the single instance of BackgroundRB on D. Is this possible? On 3/11/08 6:21 PM, "hemant kumar" <gethemant at gmail.com> wrote: Hi Noah, Sorry for late reply, I have been terribly busy with my day job and now catching up on mails. On Sun, 2008-03-09 at 15:31 -0700, Noah Horton wrote:> Hey All, > I am looking for an example of the proper config settings for > background rb to run my rails app and my backgroundrb instance on > separate machines (or more precisely, to have a rails cluster with one > backgroundrb machine). Does anyone have such examples? >Okay, so you need one BackgrounDRb server for each machine so as mongrel clusters running on that machine has access to BackgrounDRb server running on that machine? If yes, you can simply use "0.0.0.0" as ip, and your mongrels running on that machine will only use BackgrounDRb server running on that machine. Also, I will advise you to use MemCache cluster for storing status/result objects so as even if next request goes to mongrels running on another machine, you will have access to result objects from another BackgrounDRb server. I dunno, if I am answering your questions, but if you have doubt shoot back. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080312/373317fc/attachment.html
On Wed, Mar 12, 2008 at 4:04 PM, Noah Horton <noah at rapouts.com> wrote:> > I want to setup another machine, D, such that it runs nothing but > BackgroundRB. All of the mongrels on all the machines (A, B and C) would > call into the single instance of BackgroundRB on D. Is this possible?Yes that is possible and in fact as far as I know it is the preferred approach. All you need is to have the IP address or server name for the common BackgrounDRb server in a single backroundrb.yml file, which all the other machines will use. If they are all the same application code (which I assume they are), then you can just change the backgroundrb.yml file in your source control tool and then update all your servers. Regards, Ryan
Is there any config to get the backgroundrb instances to listen to requests from any machine besides localhost? On 3/12/08 1:39 PM, "Ryan Leavengood" <leavengood at gmail.com> wrote: On Wed, Mar 12, 2008 at 4:04 PM, Noah Horton <noah at rapouts.com> wrote:> > I want to setup another machine, D, such that it runs nothing but > BackgroundRB. All of the mongrels on all the machines (A, B and C) would > call into the single instance of BackgroundRB on D. Is this possible?Yes that is possible and in fact as far as I know it is the preferred approach. All you need is to have the IP address or server name for the common BackgrounDRb server in a single backroundrb.yml file, which all the other machines will use. If they are all the same application code (which I assume they are), then you can just change the backgroundrb.yml file in your source control tool and then update all your servers. Regards, Ryan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080312/2c82e9a3/attachment-0001.html
On Wed, Mar 12, 2008 at 4:47 PM, Noah Horton <noah at rapouts.com> wrote:> > Is there any config to get the backgroundrb instances to listen to requests > from any machine besides localhost?If you use the same backgroundrb.yml used for your Mongrel machines on the BackgrounDRb machine (which you should), then it should listen on the machine''s IP which you have configured in that file. If you want it to listen to all interfaces then use 0.0.0.0 like hemant said in his previous post. Regards, Ryan
Wait - the default config used in all the examples has the backgroundrb workers listening to connections from all public interfaces? That seems like a really risky thing. Perhaps the examples should all get updated to ''localhost''. On 3/12/08 2:02 PM, "Ryan Leavengood" <leavengood at gmail.com> wrote: On Wed, Mar 12, 2008 at 4:47 PM, Noah Horton <noah at rapouts.com> wrote:> > Is there any config to get the backgroundrb instances to listen to requests > from any machine besides localhost?If you use the same backgroundrb.yml used for your Mongrel machines on the BackgrounDRb machine (which you should), then it should listen on the machine''s IP which you have configured in that file. If you want it to listen to all interfaces then use 0.0.0.0 like hemant said in his previous post. Regards, Ryan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080312/c18ce75f/attachment.html
On Wed, 2008-03-12 at 14:43 -0700, Noah Horton wrote:> Wait ? the default config used in all the examples has the > backgroundrb workers listening to connections from all public > interfaces? That seems like a really risky thing. Perhaps the > examples should all get updated to ?localhost?. >Except ''localhost'' doesn''t work on Mac OSX from my experience.> > On 3/12/08 2:02 PM, "Ryan Leavengood" <leavengood at gmail.com> wrote: > > On Wed, Mar 12, 2008 at 4:47 PM, Noah Horton > <noah at rapouts.com> wrote: > > > > Is there any config to get the backgroundrb instances to > listen to requests > > from any machine besides localhost? > > If you use the same backgroundrb.yml used for your Mongrel > machines on > the BackgrounDRb machine (which you should), then it should > listen on > the machine''s IP which you have configured in that file. If > you want > it to listen to all interfaces then use 0.0.0.0 like hemant > said in > his previous post. > > Regards, > Ryan > > _______________________________________________ > Backgroundrb-devel mailing list > Backgroundrb-devel at rubyforge.org > http://rubyforge.org/mailman/listinfo/backgroundrb-devel
Then I would make the default yml file have a comment above the default saying "This doesn''t work on MacOS, you can use 0.0.0.0 but it will allow open network connections too". I would wager that 80%+ of BackgroundRB deployments have not secured this since the security implications are not noted at all. This seems really dangerous. On 3/12/08 3:52 PM, "hemant kumar" <gethemant at gmail.com> wrote: On Wed, 2008-03-12 at 14:43 -0700, Noah Horton wrote:> Wait - the default config used in all the examples has the > backgroundrb workers listening to connections from all public > interfaces? That seems like a really risky thing. Perhaps the > examples should all get updated to ''localhost''. >Except ''localhost'' doesn''t work on Mac OSX from my experience.> > On 3/12/08 2:02 PM, "Ryan Leavengood" <leavengood at gmail.com> wrote: > > On Wed, Mar 12, 2008 at 4:47 PM, Noah Horton > <noah at rapouts.com> wrote: > > > > Is there any config to get the backgroundrb instances to > listen to requests > > from any machine besides localhost? > > If you use the same backgroundrb.yml used for your Mongrel > machines on > the BackgrounDRb machine (which you should), then it should > listen on > the machine''s IP which you have configured in that file. If > you want > it to listen to all interfaces then use 0.0.0.0 like hemant > said in > his previous post. > > Regards, > Ryan > > _______________________________________________ > Backgroundrb-devel mailing list > Backgroundrb-devel at rubyforge.org > http://rubyforge.org/mailman/listinfo/backgroundrb-devel-------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080312/1092b52c/attachment.html
I am also interested in doing the same (2 servers running mongrels (IPs 158.119.147.x and 158.119.147.y) with another server (IP 158.119.147.z) running background jobs). To clarify I would have the rails apps on both x and y with the backgroundrb.yml file specifying 158.119.147.z). What would I need on the backgroundrb server- just the backgroundrb script? Would I also need a backgroundrb.yml file on this machine and does the IP here specify which machines to accept backgroundrb jobs from - would I set this to 158.119.147.0? How would I start the backgroundrb script on the background job server? Thanks for all your help Anthony On 12 Mar 2008, at 23:29, Noah Horton wrote:> Then I would make the default yml file have a comment above the > default saying ?This doesn?t work on MacOS, you can use 0.0.0.0 but > it will allow open network connections too?. > > I would wager that 80%+ of BackgroundRB deployments have not secured > this since the security implications are not noted at all. This > seems really dangerous. > > > On 3/12/08 3:52 PM, "hemant kumar" <gethemant at gmail.com> wrote: > > > > On Wed, 2008-03-12 at 14:43 -0700, Noah Horton wrote: > > Wait ? the default config used in all the examples has the > > backgroundrb workers listening to connections from all public > > interfaces? That seems like a really risky thing. Perhaps the > > examples should all get updated to ?localhost?. > > > > Except ''localhost'' doesn''t work on Mac OSX from my experience. > > > > > On 3/12/08 2:02 PM, "Ryan Leavengood" <leavengood at gmail.com> wrote: > > > > On Wed, Mar 12, 2008 at 4:47 PM, Noah Horton > > <noah at rapouts.com> wrote: > > > > > > Is there any config to get the backgroundrb instances to > > listen to requests > > > from any machine besides localhost? > > > > If you use the same backgroundrb.yml used for your Mongrel > > machines on > > the BackgrounDRb machine (which you should), then it should > > listen on > > the machine''s IP which you have configured in that file. If > > you want > > it to listen to all interfaces then use 0.0.0.0 like hemant > > said in > > his previous post. > > > > Regards, > > Ryan > > > > _______________________________________________ > > Backgroundrb-devel mailing list > > Backgroundrb-devel at rubyforge.org > > http://rubyforge.org/mailman/listinfo/backgroundrb-devel > > > _______________________________________________ > Backgroundrb-devel mailing list > Backgroundrb-devel at rubyforge.org > http://rubyforge.org/mailman/listinfo/backgroundrb-devel-------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080313/0a15c86c/attachment-0001.html
On Thu, 2008-03-13 at 16:26 +0000, Anthony Underwood wrote:> I am also interested in doing the same (2 servers running mongrels > (IPs 158.119.147.x and 158.119.147.y) with another server (IP > 158.119.147.z) running background jobs). > To clarify I would have the rails apps on both x and y with the > backgroundrb.yml file specifying 158.119.147.z).Yes that would certainly work!> > > What would I need on the backgroundrb server- just the backgroundrb > script? > Would I also need a backgroundrb.yml file on this machine and does the > IP here specify which machines to accept backgroundrb jobs from - > would I set this to 158.119.147.0? > How would I start the backgroundrb script on the background job > server?What you will need on BackgrounDRb server is the backgroundrb.yml file and your rails application ( because you want access to your rails environment in BackgrounDRB workers ). You won''t need to run any mongrels on that machine and on machines running mongrels you can just point ip of BackgrounDRB server in backgroundrb.yml file and it should suffice. Let us know, how it goes for you!> > > > > Thanks for all your help > > > > > Anthony > On 12 Mar 2008, at 23:29, Noah Horton wrote: > > > Then I would make the default yml file have a comment above the > > default saying ?This doesn?t work on MacOS, you can use 0.0.0.0 but > > it will allow open network connections too?. > > > > I would wager that 80%+ of BackgroundRB deployments have not secured > > this since the security implications are not noted at all. This > > seems really dangerous. > > > > > > On 3/12/08 3:52 PM, "hemant kumar" <gethemant at gmail.com> wrote: > > > > > > > > On Wed, 2008-03-12 at 14:43 -0700, Noah Horton wrote: > > > Wait ? the default config used in all the examples has the > > > backgroundrb workers listening to connections from all > > public > > > interfaces? That seems like a really risky thing. > > Perhaps the > > > examples should all get updated to ?localhost?. > > > > > > > Except ''localhost'' doesn''t work on Mac OSX from my > > experience. > > > > > > > > On 3/12/08 2:02 PM, "Ryan Leavengood" > > <leavengood at gmail.com> wrote: > > > > > > On Wed, Mar 12, 2008 at 4:47 PM, Noah Horton > > > <noah at rapouts.com> wrote: > > > > > > > > Is there any config to get the backgroundrb > > instances to > > > listen to requests > > > > from any machine besides localhost? > > > > > > If you use the same backgroundrb.yml used for your > > Mongrel > > > machines on > > > the BackgrounDRb machine (which you should), then > > it should > > > listen on > > > the machine''s IP which you have configured in that > > file. If > > > you want > > > it to listen to all interfaces then use 0.0.0.0 > > like hemant > > > said in > > > his previous post. > > > > > > Regards, > > > Ryan > > > > > > _______________________________________________ > > > Backgroundrb-devel mailing list > > > Backgroundrb-devel at rubyforge.org > > > http://rubyforge.org/mailman/listinfo/backgroundrb-devel > > > > > > _______________________________________________ > > Backgroundrb-devel mailing list > > Backgroundrb-devel at rubyforge.org > > http://rubyforge.org/mailman/listinfo/backgroundrb-devel > > _______________________________________________ > Backgroundrb-devel mailing list > Backgroundrb-devel at rubyforge.org > http://rubyforge.org/mailman/listinfo/backgroundrb-devel
Hi Hemant, Thanks for your help. How would it work if I have more than one rails application accessing the backgroundrb server. Would I have both rails apps on the background server and start the backgroundrb script in both applications? Thanks Anthony On 14 Mar 2008, at 04:50, hemant kumar wrote:> > On Thu, 2008-03-13 at 16:26 +0000, Anthony Underwood wrote: >> I am also interested in doing the same (2 servers running mongrels >> (IPs 158.119.147.x and 158.119.147.y) with another server (IP >> 158.119.147.z) running background jobs). >> To clarify I would have the rails apps on both x and y with the >> backgroundrb.yml file specifying 158.119.147.z). > > Yes that would certainly work! > >> >> >> What would I need on the backgroundrb server- just the backgroundrb >> script? >> Would I also need a backgroundrb.yml file on this machine and does >> the >> IP here specify which machines to accept backgroundrb jobs from - >> would I set this to 158.119.147.0? >> How would I start the backgroundrb script on the background job >> server? > > What you will need on BackgrounDRb server is the backgroundrb.yml file > and your rails application ( because you want access to your rails > environment in BackgrounDRB workers ). You won''t need to run any > mongrels on that machine and on machines running mongrels you can just > point ip of BackgrounDRB server in backgroundrb.yml file and it should > suffice. Let us know, how it goes for you! > > >> >> >> >> >> Thanks for all your help >> >> >> >> >> Anthony >> On 12 Mar 2008, at 23:29, Noah Horton wrote: >> >>> Then I would make the default yml file have a comment above the >>> default saying ?This doesn?t work on MacOS, you can use 0.0.0.0 but >>> it will allow open network connections too?. >>> >>> I would wager that 80%+ of BackgroundRB deployments have not secured >>> this since the security implications are not noted at all. This >>> seems really dangerous. >>> >>> >>> On 3/12/08 3:52 PM, "hemant kumar" <gethemant at gmail.com> wrote: >>> >>> >>> >>> On Wed, 2008-03-12 at 14:43 -0700, Noah Horton wrote: >>>> Wait ? the default config used in all the examples has the >>>> backgroundrb workers listening to connections from all >>> public >>>> interfaces? That seems like a really risky thing. >>> Perhaps the >>>> examples should all get updated to ?localhost?. >>>> >>> >>> Except ''localhost'' doesn''t work on Mac OSX from my >>> experience. >>> >>>> >>>> On 3/12/08 2:02 PM, "Ryan Leavengood" >>> <leavengood at gmail.com> wrote: >>>> >>>> On Wed, Mar 12, 2008 at 4:47 PM, Noah Horton >>>> <noah at rapouts.com> wrote: >>>>> >>>>> Is there any config to get the backgroundrb >>> instances to >>>> listen to requests >>>>> from any machine besides localhost? >>>> >>>> If you use the same backgroundrb.yml used for your >>> Mongrel >>>> machines on >>>> the BackgrounDRb machine (which you should), then >>> it should >>>> listen on >>>> the machine''s IP which you have configured in that >>> file. If >>>> you want >>>> it to listen to all interfaces then use 0.0.0.0 >>> like hemant >>>> said in >>>> his previous post. >>>> >>>> Regards, >>>> Ryan >>>> >>>> _______________________________________________ >>>> Backgroundrb-devel mailing list >>>> Backgroundrb-devel at rubyforge.org >>>> http://rubyforge.org/mailman/listinfo/backgroundrb-devel >>> >>> >>> _______________________________________________ >>> Backgroundrb-devel mailing list >>> Backgroundrb-devel at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/backgroundrb-devel >> >> _______________________________________________ >> Backgroundrb-devel mailing list >> Backgroundrb-devel at rubyforge.org >> http://rubyforge.org/mailman/listinfo/backgroundrb-devel >
On Fri, 2008-03-14 at 08:49 +0000, Anthony Underwood wrote:> Hi Hemant, > > Thanks for your help. How would it work if I have more than one rails > application accessing the backgroundrb server. Would I have both rails > apps on the background server and start the backgroundrb script in > both applications? >Out of box, you can''t/shouldn''t access same backgroundrb server from two different rails application( i.e entirely different rails application, you can very well access backgroundrb server from any instances of same rails applications). So, If you want to have more than one rails application (that''s to say with different code base) using same bdrb server, you will have to setup rails environment of bdrb server so as models/libs/plugins used in both applications are present in bdrb server''s rails instance.This is tricky and I won''t advise you to go with this. However, you can have two instances of bdrb servers, running on same machine, but different ports, being used from different rails applications.> Thanks > > Anthony > > On 14 Mar 2008, at 04:50, hemant kumar wrote: > > > > > On Thu, 2008-03-13 at 16:26 +0000, Anthony Underwood wrote: > >> I am also interested in doing the same (2 servers running mongrels > >> (IPs 158.119.147.x and 158.119.147.y) with another server (IP > >> 158.119.147.z) running background jobs). > >> To clarify I would have the rails apps on both x and y with the > >> backgroundrb.yml file specifying 158.119.147.z). > > > > Yes that would certainly work! > > > >> > >> > >> What would I need on the backgroundrb server- just the backgroundrb > >> script? > >> Would I also need a backgroundrb.yml file on this machine and does > >> the > >> IP here specify which machines to accept backgroundrb jobs from - > >> would I set this to 158.119.147.0? > >> How would I start the backgroundrb script on the background job > >> server? > > > > What you will need on BackgrounDRb server is the backgroundrb.yml file > > and your rails application ( because you want access to your rails > > environment in BackgrounDRB workers ). You won''t need to run any > > mongrels on that machine and on machines running mongrels you can just > > point ip of BackgrounDRB server in backgroundrb.yml file and it should > > suffice. Let us know, how it goes for you! > > > > > >> > >> > >> > >> > >> Thanks for all your help > >> > >> > >> > >> > >> Anthony > >> On 12 Mar 2008, at 23:29, Noah Horton wrote: > >> > >>> Then I would make the default yml file have a comment above the > >>> default saying ?This doesn?t work on MacOS, you can use 0.0.0.0 but > >>> it will allow open network connections too?. > >>> > >>> I would wager that 80%+ of BackgroundRB deployments have not secured > >>> this since the security implications are not noted at all. This > >>> seems really dangerous. > >>> > >>> > >>> On 3/12/08 3:52 PM, "hemant kumar" <gethemant at gmail.com> wrote: > >>> > >>> > >>> > >>> On Wed, 2008-03-12 at 14:43 -0700, Noah Horton wrote: > >>>> Wait ? the default config used in all the examples has the > >>>> backgroundrb workers listening to connections from all > >>> public > >>>> interfaces? That seems like a really risky thing. > >>> Perhaps the > >>>> examples should all get updated to ?localhost?. > >>>> > >>> > >>> Except ''localhost'' doesn''t work on Mac OSX from my > >>> experience. > >>> > >>>> > >>>> On 3/12/08 2:02 PM, "Ryan Leavengood" > >>> <leavengood at gmail.com> wrote: > >>>> > >>>> On Wed, Mar 12, 2008 at 4:47 PM, Noah Horton > >>>> <noah at rapouts.com> wrote: > >>>>> > >>>>> Is there any config to get the backgroundrb > >>> instances to > >>>> listen to requests > >>>>> from any machine besides localhost? > >>>> > >>>> If you use the same backgroundrb.yml used for your > >>> Mongrel > >>>> machines on > >>>> the BackgrounDRb machine (which you should), then > >>> it should > >>>> listen on > >>>> the machine''s IP which you have configured in that > >>> file. If > >>>> you want > >>>> it to listen to all interfaces then use 0.0.0.0 > >>> like hemant > >>>> said in > >>>> his previous post. > >>>> > >>>> Regards, > >>>> Ryan > >>>> > >>>> _______________________________________________ > >>>> Backgroundrb-devel mailing list > >>>> Backgroundrb-devel at rubyforge.org > >>>> http://rubyforge.org/mailman/listinfo/backgroundrb-devel > >>> > >>> > >>> _______________________________________________ > >>> Backgroundrb-devel mailing list > >>> Backgroundrb-devel at rubyforge.org > >>> http://rubyforge.org/mailman/listinfo/backgroundrb-devel > >> > >> _______________________________________________ > >> Backgroundrb-devel mailing list > >> Backgroundrb-devel at rubyforge.org > >> http://rubyforge.org/mailman/listinfo/backgroundrb-devel > > >
Thanks, Sorry to be a bit slow. So to clarify I would have copies of each rails app on the backgroundrb machine where the port in the backgroundrb.yml has been set to different values. I would then start several backgroundrb instances (one for each app) by running script/ backgroundrb start within app. Thanks Anthony On 14 Mar 2008, at 09:18, hemant kumar wrote:> > On Fri, 2008-03-14 at 08:49 +0000, Anthony Underwood wrote: >> Hi Hemant, >> >> Thanks for your help. How would it work if I have more than one rails >> application accessing the backgroundrb server. Would I have both >> rails >> apps on the background server and start the backgroundrb script in >> both applications? >> > > Out of box, you can''t/shouldn''t access same backgroundrb server from > two > different rails application( i.e entirely different rails application, > you can very well access backgroundrb server from any instances of > same > rails applications). > > So, If you want to have more than one rails application (that''s to say > with different code base) using same bdrb server, you will have to > setup > rails environment of bdrb server so as models/libs/plugins used in > both > applications are present in bdrb server''s rails instance.This is > tricky > and I won''t advise you to go with this. > > However, you can have two instances of bdrb servers, running on same > machine, but different ports, being used from different rails > applications. > > > > >> Thanks >> >> Anthony >> >> On 14 Mar 2008, at 04:50, hemant kumar wrote: >> >>> >>> On Thu, 2008-03-13 at 16:26 +0000, Anthony Underwood wrote: >>>> I am also interested in doing the same (2 servers running mongrels >>>> (IPs 158.119.147.x and 158.119.147.y) with another server (IP >>>> 158.119.147.z) running background jobs). >>>> To clarify I would have the rails apps on both x and y with the >>>> backgroundrb.yml file specifying 158.119.147.z). >>> >>> Yes that would certainly work! >>> >>>> >>>> >>>> What would I need on the backgroundrb server- just the backgroundrb >>>> script? >>>> Would I also need a backgroundrb.yml file on this machine and does >>>> the >>>> IP here specify which machines to accept backgroundrb jobs from - >>>> would I set this to 158.119.147.0? >>>> How would I start the backgroundrb script on the background job >>>> server? >>> >>> What you will need on BackgrounDRb server is the backgroundrb.yml >>> file >>> and your rails application ( because you want access to your rails >>> environment in BackgrounDRB workers ). You won''t need to run any >>> mongrels on that machine and on machines running mongrels you can >>> just >>> point ip of BackgrounDRB server in backgroundrb.yml file and it >>> should >>> suffice. Let us know, how it goes for you! >>> >>> >>>> >>>> >>>> >>>> >>>> Thanks for all your help >>>> >>>> >>>> >>>> >>>> Anthony >>>> On 12 Mar 2008, at 23:29, Noah Horton wrote: >>>> >>>>> Then I would make the default yml file have a comment above the >>>>> default saying ?This doesn?t work on MacOS, you can use 0.0.0.0 >>>>> but >>>>> it will allow open network connections too?. >>>>> >>>>> I would wager that 80%+ of BackgroundRB deployments have not >>>>> secured >>>>> this since the security implications are not noted at all. This >>>>> seems really dangerous. >>>>> >>>>> >>>>> On 3/12/08 3:52 PM, "hemant kumar" <gethemant at gmail.com> wrote: >>>>> >>>>> >>>>> >>>>> On Wed, 2008-03-12 at 14:43 -0700, Noah Horton wrote: >>>>>> Wait ? the default config used in all the examples has the >>>>>> backgroundrb workers listening to connections from all >>>>> public >>>>>> interfaces? That seems like a really risky thing. >>>>> Perhaps the >>>>>> examples should all get updated to ?localhost?. >>>>>> >>>>> >>>>> Except ''localhost'' doesn''t work on Mac OSX from my >>>>> experience. >>>>> >>>>>> >>>>>> On 3/12/08 2:02 PM, "Ryan Leavengood" >>>>> <leavengood at gmail.com> wrote: >>>>>> >>>>>> On Wed, Mar 12, 2008 at 4:47 PM, Noah Horton >>>>>> <noah at rapouts.com> wrote: >>>>>>> >>>>>>> Is there any config to get the backgroundrb >>>>> instances to >>>>>> listen to requests >>>>>>> from any machine besides localhost? >>>>>> >>>>>> If you use the same backgroundrb.yml used for your >>>>> Mongrel >>>>>> machines on >>>>>> the BackgrounDRb machine (which you should), then >>>>> it should >>>>>> listen on >>>>>> the machine''s IP which you have configured in that >>>>> file. If >>>>>> you want >>>>>> it to listen to all interfaces then use 0.0.0.0 >>>>> like hemant >>>>>> said in >>>>>> his previous post. >>>>>> >>>>>> Regards, >>>>>> Ryan >>>>>> >>>>>> _______________________________________________ >>>>>> Backgroundrb-devel mailing list >>>>>> Backgroundrb-devel at rubyforge.org >>>>>> http://rubyforge.org/mailman/listinfo/backgroundrb-devel >>>>> >>>>> >>>>> _______________________________________________ >>>>> Backgroundrb-devel mailing list >>>>> Backgroundrb-devel at rubyforge.org >>>>> http://rubyforge.org/mailman/listinfo/backgroundrb-devel >>>> >>>> _______________________________________________ >>>> Backgroundrb-devel mailing list >>>> Backgroundrb-devel at rubyforge.org >>>> http://rubyforge.org/mailman/listinfo/backgroundrb-devel >>> >> >