nginx reverse proxy cache manager

[naturallymitchell]

when new content is created, add it to the cache
when content is updated, remove it and re-add it to the cache
.. or just whenever json-interface/create_document.action runs, invalidate that document and request it from nginx
we should send ETag hash to make this easier
we'd need to update lists too, but that's pretty difficult without indexes

https://github.com/perusio/nginx-cache-purge/blob/master/nginx-cache-purge
https://www.nginx.com/blog/nginx-caching-guide/
https://serverfault.com/questions/549200/how-do-i-force-nginx-to-load-new-static-files
https://stackoverflow.com/questions/6236078/how-to-clear-the-cache-of-nginx
http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_cache_path

[dariusc93]

Sounds like it would be better to let nginx handle most the caching than to make a manager to do that since it would usually be nginx delivering the content. Also, is there any other type of content is being created and/or updated outside of the json-interface because the last I recall, the content created for that is already saved to disk by it and it reads from disk when it finds a specific key in header.

[naturallymitchell]

let nginx handle most the caching than to make a manager to do that

how will nginx know which version it has compared to the latest?