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

Aggressive caching #119

Open
Apexal opened this issue Jun 12, 2023 · 1 comment
Open

Aggressive caching #119

Apexal opened this issue Jun 12, 2023 · 1 comment
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@Apexal
Copy link
Member

Apexal commented Jun 12, 2023

Most data will not change, especially for non-active semesters. We can aggressively cache all non-active semester data, and include active semester data like projects, enrollments, etc. Basically everything besides meetings and attendance can be aggressively cached.

@Apexal Apexal added the enhancement New feature or request label Jun 12, 2023
@Apexal Apexal added this to the Fall 2023 milestone Jun 12, 2023
@Apexal Apexal self-assigned this Jun 12, 2023
@Apexal
Copy link
Member Author

Apexal commented Sep 5, 2023

We can and should cache GitHub API responses for repo metadata so we don't get rate-limited.

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
None yet
Development

No branches or pull requests

1 participant