indexzero / nconf-redis Goto Github PK
View Code? Open in Web Editor NEWA redis store for nconf
Home Page: http://github.com/indexzero/nconf-redis
License: MIT License
A redis store for nconf
Home Page: http://github.com/indexzero/nconf-redis
License: MIT License
Is this project not being maintained?
.get() throws a type-error if one queries for an undefined key.
If you have an JSON key that contains some null values it will throw an exception when you try to save the key.
TL;DR
demo of the issue: https://gist.github.com/itayw/7566317
JSON example:
var badJSON = {
port: 40008,
securePort: null
}
Fails on:
-->nconf.set('badJSON', badJSON, function(err) {
if (err)
throw err;
nconf.get('badJSON', function(err, value) {
if (err)
throw err;
if (value)
console.log('bad JSON value set and get fine.');
else
console.log('Failed to set and get bad JSON value')
});
});
Exception and stack:
TypeError: Object.keys called on non-object
at Function.keys (native)
at Redis._setObject (/.../dev/joola.io.manage/node_modules/nconf-redis/lib/nconf-redis.js:425:23)
...
Hi there,
I've been tracking down an issue with nconf and I noticed that I wasn't able to run any tests in this repo at all. I'm getting a bit of a strange error that seems to error out before any test has started:
> [email protected] test /Users/mansona/git/blooie/public/nconf-redis
> vows test/*-test.js --spec
♢ nconf/stores/redis
util.puts: Use console.log instead
✗ Errored » 1 errored
npm ERR! Test failed. See above for more details.
Here are my current versions of node and npm:
➜ nconf-redis git:(master) node -v
v1.2.0
➜ nconf-redis git:(master) npm -v
2.5.1
Has anyone had any issues running these tests recently?
Hi
Before creating our own implementation, I was researching the scene for a Redis based configuration solution with in-memory fallback, and got here - which is awsome!
(My last visit to nconf was years ago, back then we chose another solution)
Now, assume that we use redis
as the central configuration server, and would like to keep all clients in sync for config changes pushed to the sever - the natural choice would be to use the pubsub capabilities of redis
, to keep all subscribed clients in sync with changes - thus, allowing the end users to use synchronous API - just like with memory storage.
I'm very hoping I'm not the first one to think about it...
Thoughts? References? Advices?
If it means submitting a new nconf-storage - it's considerable too, if I get some guidance to be sure I'm coding in accord to your paradigm.
I've used redis
s pubsub channels with node for a chat, and it works like a charm. Sure a configuration center will be easier than that...
Thanks
Osher
This is what I have so far:
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.