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

[Feature]: Add the possibility to set a time caching for VT #515

Open
FafnerKeyZee opened this issue Sep 14, 2022 · 1 comment
Open

[Feature]: Add the possibility to set a time caching for VT #515

FafnerKeyZee opened this issue Sep 14, 2022 · 1 comment
Labels
good first issue This is a relatively simple issue that can be fixed without knowing too much about the project. New Features

Comments

@FafnerKeyZee
Copy link
Contributor

Is your feature request related to a problem? Please describe.

Currently the cache for the VT module is 24h, it might be nice to be able to change the duration to a shorter timeframe depending on the user's API keys

Describe the solution you'd like

Add an option in the config file to set a personal timer :)

Describe alternatives you've considered

No response

Additional context

No response

@Rafiot Rafiot added the good first issue This is a relatively simple issue that can be fixed without knowing too much about the project. label Oct 26, 2022
@Rafiot
Copy link
Member

Rafiot commented Oct 26, 2022

Right now, Lookyloo uses the date as a key to decide if it should re-trigger the capture or not. It is a bit dirty but changing it is quite a bit of work for a limited usecase: it is already possible to force re-trigger the modules if the user wishes to get a fresher result the same day.

But if someone is interested in understanding the internals of Lookyloo, it is a good first issue I could help with.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue This is a relatively simple issue that can be fixed without knowing too much about the project. New Features
Projects
None yet
Development

No branches or pull requests

2 participants