[GH-ISSUE #34] can support redis backend? #173

Closed
opened 2026-03-01 17:24:21 +03:00 by kerem · 4 comments
Owner

Originally created by @millken on GitHub (Apr 10, 2013).
Original GitHub issue: https://github.com/abh/geodns/issues/34

Originally created by @millken on GitHub (Apr 10, 2013). Original GitHub issue: https://github.com/abh/geodns/issues/34
kerem closed this issue 2026-03-01 17:24:21 +03:00
Author
Owner

@abh commented on GitHub (Apr 10, 2013):

What did you have in mind that you'd like stored in redis?

<!-- gh-comment-id:16187115 --> @abh commented on GitHub (Apr 10, 2013): What did you have in mind that you'd like stored in redis?
Author
Owner

@millken commented on GitHub (Apr 11, 2013):

yes, or stored in other db.

<!-- gh-comment-id:16213662 --> @millken commented on GitHub (Apr 11, 2013): yes, or stored in other db.
Author
Owner

@abh commented on GitHub (Apr 11, 2013):

It's not something I have on the short-term roadmap, but it wouldn't be impossible to implement. I don't update the zone data more than every few minutes and my files only have a few tens of thousands of entries, so the current system works fine for me.

What are you trying to do that needs a database backend instead of just rsyncing the json files?

<!-- gh-comment-id:16250944 --> @abh commented on GitHub (Apr 11, 2013): It's not something I have on the short-term roadmap, but it wouldn't be impossible to implement. I don't update the zone data more than every few minutes and my files only have a few tens of thousands of entries, so the current system works fine for me. What are you trying to do that needs a database backend instead of just rsyncing the json files?
Author
Owner

@abh commented on GitHub (Feb 19, 2015):

Closing for now; @millken let me know if you have some ideas and we can re-open the issue.

<!-- gh-comment-id:75018449 --> @abh commented on GitHub (Feb 19, 2015): Closing for now; @millken let me know if you have some ideas and we can re-open the issue.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/geodns#173
No description provided.