Hi Alex,
That is the version I am using. I presume you are saying that I do
not have to bother with any of those YAML files, which I didn't
(because I didn't know how to use them in the first place) so I still
don't know what to do to make my Rails instance connect to
"juggernaut", i.e. redis as you say.
Assuming I have my "Rails Stack" running on Server A, I want to run
"Juggernaut" on a different server, Server B. Juggernaut needs
node.js AND redis, so do I put both of these on Server B? If I do,
how do I tell my rails application (on server A) that
"juggernaut" (node.js and/or redis) lives on Server B?
As I see it, there are 2 touchpoints between my Rails application and
Juggernaut.
1. In my rails views, I have the clients connect to juggernaut using
the following JS (this comes straight from my application and works on
the one server configuration):
var jug = new Juggernaut;
How does it know where "Juggernaut" is? How does just this line
connect to the correct server/service?
2. In my controllers when they publish to Juggernaut (again, straight
from my code):
Juggernaut.publish("channel1", "User commented") rescue nil
Again, where does it say it needs to publish to, where does it say
publish this to "Juggernaut" (redis) on Server B?
Cheers,
Mark.