Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't configure reds to use a redis server other then localhost #3

Closed
dinedal opened this issue Aug 8, 2011 · 5 comments
Closed

Can't configure reds to use a redis server other then localhost #3

dinedal opened this issue Aug 8, 2011 · 5 comments

Comments

@dinedal
Copy link

dinedal commented Aug 8, 2011

This is needed to use HEAD of kue in environments where redis doesn't live on the same machine.

@tj
Copy link
Owner

tj commented Aug 8, 2011

right right. We should lazy-create the reds connection in Kue, then you can override exports.createClient

@gtramontina
Copy link

Yep. You can do something like:

var client = redis.createClient(port, host);
client.auth(password, function() {
reds.client = client; // <- This is where you specify which client reds will use.
var search = reds.createSearch('namespace');
...
});

Correct, @visionmedia?

@dinedal
Copy link
Author

dinedal commented Aug 10, 2011

@gtramontina Yes, that works great when using reds without kue, perhaps this issue belongs on kue's tracker then? The connection for reds is hardcoded to be local host in kue.

@tj
Copy link
Owner

tj commented Aug 10, 2011

yeah we have this issue open in kue

@tj tj closed this as completed Aug 10, 2011
@plus-
Copy link
Contributor

plus- commented May 16, 2013

Maybe @gtramontina sample could go in the Readme documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants