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

Cache not flushed on updates #5

Open
raphael opened this issue Jul 17, 2016 · 2 comments
Open

Cache not flushed on updates #5

raphael opened this issue Jul 17, 2016 · 2 comments
Labels

Comments

@raphael
Copy link

raphael commented Jul 17, 2016

Each time I release a new version of the site I need to manually flush memcache from the console. Is that expected? It seems CacheKey should use the current version to build the key, this would guarantee that the correct files are being served.

@x1ddos
Copy link
Contributor

x1ddos commented Oct 10, 2016

@raphael cache is invalidated on object changes in your GCS bucket. It is done by setting an Object Change Notification web hook to this handler:

http.HandleFunc(config.HookPath, storage.HandleChangeHook)

I admit the documentation is completely lacking on this. I'm planning to address it shortly.

@x1ddos x1ddos added the docs label Oct 10, 2016
@raphael
Copy link
Author

raphael commented Oct 10, 2016

Thanks! looking forward to it.

x1ddos pushed a commit that referenced this issue Apr 5, 2017
Removed default GAE config (app.yaml) and init func
to allow importing packages use their own configuration.

Package users have to provide their own GAE configuration
and an init func, but server package docs include a usage
example (updates #5).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants