Closed mccalluc closed 7 years ago
... but worth noting that in each of these, nginx is not just acting as a reverse proxy, as far as I can tell: Once the file is on the server, it looks like the preferred thing is to process it in place, rather than trying to squeeze it through http again. ie, all this machinery doesn't do much more than just having a volume mounted to docker, and having a hook to trigger ingest of a given file.
If a special build is required, then I should probably step back and take another look at having separate containers for nginx and django, because I don't want to add all the steps for the nginx build to the existing Dockerfile.
Gave up on trying to do it through HTTP: CLI works.
There are several options for multi-POST, big file uploads:
Figure out what works best, install it, and figure out the client scripting needed to make it useful.