Skip to content
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

Migrate blacklist functionality to file #97

Open
ezeoleaf opened this issue Dec 2, 2022 · 0 comments
Open

Migrate blacklist functionality to file #97

ezeoleaf opened this issue Dec 2, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@ezeoleaf
Copy link
Owner

ezeoleaf commented Dec 2, 2022

Is your feature request related to a problem? Please describe.
Yes, Redis is not keeping the blacklist keys indefinitely, so ideally we will read from a blacklist file every 5 minutes and load the blacklisted repositories in memory to be used as our cache.

Describe the solution you'd like
See above

Describe alternatives you've considered
Perhaps a db but that could be messier. Or instead of a go routine, using an endpoint to accept new repository to blacklist and then update the blacklisted list.

Additional context
-

@ezeoleaf ezeoleaf added the enhancement New feature or request label Dec 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: No status
Development

No branches or pull requests

1 participant