-
Notifications
You must be signed in to change notification settings - Fork 8
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
Add Redis backend #8
Conversation
a6c29c0
to
fb67ed9
Compare
A few updates:
|
We've been using this for a few weeks now and it seems to be working well. |
Note: - The test code checks that it gets "Expired" for expired keys. But keeping expired keys around seems pointless, so for the Redis checks I allow it to return Not_found instead.
Would be good to get this merged, because it's a dependency of datakit-ci and we can't release that to opam-repository until this is released. |
Thanks for merging! Any chance of a release in opam-repository stable containing this, so that we can release the CI software as well? |
Thanks! I've updated DataKitCI to use the released version. |
thanks @seliopou! |
Notes:
The test code checks that it gets "Expired" for expired keys. But keeping expired keys around seems pointless, so for the Redis checks I allow it to return Not_found instead.
The tests assume you have a Redis server running on 127.0.0.1, which probably isn't reasonable. Maybe they should be disabled. How does it work for Postgres?
Fixes #3.
Has only been very lightly tested so far.