Multiple Instances Of backgrounDRb

Rails
1

I have an application setup as follows:

Core code is in:

/home/subdomain1/current
accessed at subdomain1.domain.com

I then have various instances of this app that are sym-linked to the
core (minus a custom config file and views) setup like:

/home/subdomain2/current
accessed at subdomain2.domain.com

I have backgrounDRb running to update a cache of RSS files.

Is there a way to get all instances of the app to share the single
backgrounDRb - or should each app start it’s own backgrounDRb (rake
backgroundrb:start)? Whichever is the best way - how do I do it?

I have tried starting a second instance of backgrounDRb in subdomain2,
but it never seems to start more than 1.

I have tried just running a single instance in subdomain1, but it
doesn’t appear that app in subdomain2 can get at it.

Thanks!!!

2

better ask on backgroundrb mailing list.

3

Hemant K. wrote:

better ask on backgroundrb mailing list.

I would love to, but for some reason I can never get to rubyforge.org.
I tried doing a traceroute and I’m not getting blocked at my ISP -
perhaps rubyforge.org is blocking the block of IP’s from my ISP? But
it’s weird because I can get to rubyforge.org subdomains - like
backgroundrb.rubyforge.org no problem.

So anyway, I can’t access the backgroundrb mailing list on
rubyforge.org.

4

On Jul 31, 2006, at 5:41 PM, justin Pease wrote:

/home/subdomain2/current

I have tried just running a single instance in subdomain1, but it
doesn’t appear that app in subdomain2 can get at it.

Thanks!!!

– Posted via http://www.ruby-forum.com/.

Yeah there shouldn't be a problem running just one drb server for

multiple apps. Just make sure you have the plugin installed in both
apps. But you only start the drb server from one app. And whichever
app you use to start the drb server in is the one that contains the
workers in lib/workers as well.

-Ezra