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!!! -- Posted via http://www.ruby-forum.com/.
better ask on backgroundrb mailing list. On 8/1/06, justin Pease <public@nuance9.com> wrote:> > 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!!! > > -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > Rails mailing list > Rails@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails >-- nothing much to talk -------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060801/a98f391e/attachment.html
Hemant Kumar 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. -- Posted via http://www.ruby-forum.com/.
On Jul 31, 2006, at 5:41 PM, justin Pease wrote:> 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!!! > > -- 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