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

[OPS] Automation around purging #519

Open
rgbkrk opened this issue Oct 18, 2015 · 1 comment
Open

[OPS] Automation around purging #519

rgbkrk opened this issue Oct 18, 2015 · 1 comment
Labels
type:Maintenance An enhancement to the architecture or maintenance of this project

Comments

@rgbkrk
Copy link
Member

rgbkrk commented Oct 18, 2015

Right now, when we make a deploy or update the image it likely doesn't look very live because most pages are cached by Fastly. Independently of this repo, we should trigger the purge against fastly for nbviewer.

@yuvipanda
Copy link
Contributor

https://docs.fastly.com/api/purge has references on how to purge. It allows us to purge everything, which we could possibly do on each deploy (not sure how much additional load it would put on servers?).

At Wikimedia, cached HTML (for logged out users, in article views) is set to cache for 30 days only, producing a nice and gradual turnover without too much cache issues.

@parente parente added the type:Maintenance An enhancement to the architecture or maintenance of this project label Jul 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:Maintenance An enhancement to the architecture or maintenance of this project
Projects
None yet
Development

No branches or pull requests

3 participants