{"action":"created","issue":{"url":"https://api.github.com/repos/indexzero/nconf-redis/issues/12","repository_url":"https://api.github.com/repos/indexzero/nconf-redis","labels_url":"https://api.github.com/repos/indexzero/nconf-redis/issues/12/labels{/name}","comments_url":"https://api.github.com/repos/indexzero/nconf-redis/issues/12/comments","events_url":"https://api.github.com/repos/indexzero/nconf-redis/issues/12/events","html_url":"https://github.com/indexzero/nconf-redis/issues/12","id":137510064,"number":12,"title":"using the pubsub capability of redis to be updated with config changes","user":{"login":"osher","id":803101,"avatar_url":"https://avatars.githubusercontent.com/u/803101?v=3","gravatar_id":"","url":"https://api.github.com/users/osher","html_url":"https://github.com/osher","followers_url":"https://api.github.com/users/osher/followers","following_url":"https://api.github.com/users/osher/following{/other_user}","gists_url":"https://api.github.com/users/osher/gists{/gist_id}","starred_url":"https://api.github.com/users/osher/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/osher/subscriptions","organizations_url":"https://api.github.com/users/osher/orgs","repos_url":"https://api.github.com/users/osher/repos","events_url":"https://api.github.com/users/osher/events{/privacy}","received_events_url":"https://api.github.com/users/osher/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2016-03-01T08:44:23Z","updated_at":"2016-10-30T05:10:10Z","closed_at":null,"body":"Hi \r\n\r\nBefore 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!* \r\n(My last visit to nconf was years ago, back then we chose another solution)\r\n\r\nNow, 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.\r\n\r\nI'm very hoping I'm not the first one to think about it...\r\n\r\nThoughts? References? Advices?\r\n\r\nIf 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.\r\nI'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...\r\n\r\nThanks\r\n   Osher\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/indexzero/nconf-redis/issues/comments/257132499","html_url":"https://github.com/indexzero/nconf-redis/issues/12#issuecomment-257132499","issue_url":"https://api.github.com/repos/indexzero/nconf-redis/issues/12","id":257132499,"user":{"login":"fruch","id":340979,"avatar_url":"https://avatars.githubusercontent.com/u/340979?v=3","gravatar_id":"","url":"https://api.github.com/users/fruch","html_url":"https://github.com/fruch","followers_url":"https://api.github.com/users/fruch/followers","following_url":"https://api.github.com/users/fruch/following{/other_user}","gists_url":"https://api.github.com/users/fruch/gists{/gist_id}","starred_url":"https://api.github.com/users/fruch/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fruch/subscriptions","organizations_url":"https://api.github.com/users/fruch/orgs","repos_url":"https://api.github.com/users/fruch/repos","events_url":"https://api.github.com/users/fruch/events{/privacy}","received_events_url":"https://api.github.com/users/fruch/received_events","type":"User","site_admin":false},"created_at":"2016-10-30T05:10:10Z","updated_at":"2016-10-30T05:10:10Z","body":"I've found node-config-live which does exactly this, it works wit node-config-live, I guess it could work with nconf easily"}}
{"actor":{"display_login":"fruch"}}