Kue 0.8.6 Redis always tries to connect to localhost
See original GitHub issueI’m attempting to upgrade Kue to the latest nom version (0.8.6). We have Kue 0.5 with the monkey-patch to get it connect to a remote redis and this works fine. I’ve removed the monkey patch and set up the following code:
var kue = require('kue');
var jobs = kue.createQueue({
prefix: 'q',
redis: {
port:6379,
host:'192.168.0.47',
options:
}
}
});
…yet Kue is still connecting to localhost and ignores the redis settings. Why is this? What have I overlooked?
Issue Analytics
- State:
- Created 9 years ago
- Comments:5
Top Results From Across the Web
node.js - Connecting to redis using kue always creates a ...
I used a different way to setup the connection and it works so far this is what I've done: app.redisClient = redis.createClient(config.redisPort, config....
Read more >Configuration | StackExchange.Redis
We run this command to verify that we have a valid connection to the Redis service. Because there are lots of different ways...
Read more >Troubleshoot connecting to an ElastiCache for Redis cluster
If you recently created the cluster, verify that the cluster creation completed and that the cluster is ready to accept connections.
Read more >How to Use Redis With Python
In this step-by-step tutorial, you'll cover how to use both Redis and its Python client library. You'll learn a bite-sized slice of Redis...
Read more >Introduction to Lettuce - the Java Redis Client - Baeldung
Learn how to use Lettuce to connect and query a Redis server from within our ... RedisClient .create("redis://password@localhost:6379/"); ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The missing { was a typo - apologies. However, your comments have helped. There was no access to any Kue resource prior to createQueue - but there was a separate express server being instantiated. Moving createQueue above this step has got Kue trying to connect to the correct IP. The problem now is that I’m seeing an error:
Many thanks for you help with this
happy for you 😃