> Is there a reason why you need nginx "cache" instead of just storing the
files statically?
I don't have a big enough disk to store *all* user uploaded files
accumulated over the years. So I need some way to manage a pool of space to
store hot uploads.
> One way would be instead of using the ca
> One option is to keep a copy of the file on disk (outside of the nginx
cache). Then use something like try_files to read it, and have that response
be cached by nginx. But then I end up with 2 of the files on disk (one in my
try_files directory, and one in the nginx cache). I also need to manuall
I have nginx setup to proxy file uploads. The file upload streams into
nginx, goes into my upstream, and then the upstream streams it to Amazon S3
(after some basic processing). In addition to proxying the upload, I also
want to proxy the download, with some caching on the nginx side.
It would be
