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.

Sign up for GitHub

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

Jump to bottom

Introduce a caching workaround #1

Closed
1 task done
eoussama opened this issue Jul 11, 2020 · 1 comment
Closed
1 task done

Introduce a caching workaround #1

eoussama opened this issue Jul 11, 2020 · 1 comment
Assignees
@eoussama
Labels
API Related to the API Enhancement New feature or request Good first issue Good for newcomers

Comments

@eoussama
Copy link
Owner

eoussama commented Jul 11, 2020 •
edited
Loading

To avoid spamming the scrapping targets, there needs to exist a caching workaround that does not utilize any in-memory caching libraries. Dumping the data in a JSON file would do the trick.

The dump file should be updated frequently, based on a scheduler of a 1-day interval would be preferable.

  • Dumping the data into a JSON file
  • [ ] Frequent updates to the dump file
@eoussama eoussama self-assigned this Jul 11, 2020
@eoussama eoussama added Enhancement New feature or request Good first issue Good for newcomers labels Jul 11, 2020
@eoussama
Copy link
Owner Author

eoussama commented Nov 20, 2020 •
edited
Loading

Continued in #3

@eoussama eoussama reopened this Nov 20, 2020
@eoussama eoussama added the API Related to the API label Dec 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@eoussama eoussama

Labels
API Related to the API Enhancement New feature or request Good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@eoussama