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

Page and permissions caching #714

Closed
ian-ross opened this issue Sep 22, 2016 · 4 comments
Closed

Page and permissions caching #714

ian-ross opened this issue Sep 22, 2016 · 4 comments
Assignees
@ian-ross @amplifi
Labels
bug priority: medium
Milestone
Sprint 10

Comments

@ian-ross
Copy link
Contributor

At the moment, we don't use any page caching, and there is some ad hoc caching within django-tutelary that is dangerous for a multi-process environment such as the UWSGI-based setup we use in production. To fix both of these issues, we should switch to using the Django caching framework in django-tutelary (Cadasta/django-tutelary#32) and should then set up memcached-based caching in production.
@ian-ross ian-ross added this to the Sprint 9 milestone Sep 22, 2016
@dpalomino dpalomino modified the milestones: Sprint 10, Sprint 9 Oct 17, 2016
@amplifi
Copy link
Contributor

amplifi commented Oct 17, 2016

Memcached instance is up and running on staging.

@amplifi
Copy link
Contributor

amplifi commented Oct 25, 2016

Live in demo and prod.

@oliverroick
Copy link
Member

Can we close it then, or is there more to do?

@amplifi
Copy link
Contributor

amplifi commented Oct 25, 2016

@oliverroick Good to close from my side; @ian-ross ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ian-ross ian-ross

@amplifi amplifi

Labels
bug priority: medium
Projects
None yet
Milestone
Sprint 10
Development

No branches or pull requests
5 participants
@oliverroick @seav @ian-ross @amplifi @dpalomino