[Backgroundrb-devel] Using the ip flag

Anthony Underwood email2ants at gmail.com
Fri Mar 14 04:49:11 EDT 2008


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
>



More information about the Backgroundrb-devel mailing list