Repository navigation
Use Django caching - #809
Merged
Merged
Conversation
development environments which will use Dummy Caching (https://docs.djangoproject.com/en/4.1/topics/cache/#dummy-caching-for-development) Site wide cache will stored in cache_table, to run this initially the command of `python manage.py createcachetable` will need to be run after the deployment of this feature.
…on in deployment scripts
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What GitHub issue does this PR apply to?
Issue
#487
PR
#646
What changed and why?
Since @LittleBigProgramming 's original PR to do caching, I unfortunately hadn't really tested it and time passed and the code base strayed from those commits. But I wanted to still implement it, and use @LittleBigProgramming 's original code if possible.
This pulls in their changes, then fixes things that evolved, notably that Django 4.x is now Django 6.x. The original intent is still there, just tried to resolve any issues that came up after.
(It does mean I'll have to close #646 though, sorry!)
It also adds some extra security, linting, and other checks into the CI process, and likely will break upon merging.
AI bots used in the process of making this PR
OpenCode's Big Pickle model
Review and some manual work by myself
Checklist
Any additional comments or things to be aware of while reviewing?
An extra thank you again to @LittleBigProgramming , who's contributed a lot to this project over the years!