mccalluc
commented
7 years ago @pkerpedjiev / @ngehlenborg : I am doing this the wrong way. I'm wondering if file upload should really be something we do via http, or if it'd make more sense to do it via manage.py. For an admin activity like this, it's not unreasonable that it be done via the command line, and it would save us trouble other places, too:
- Don't need to worry about ad hoc user creation
- Don't need to worry about django instances that didn't get reaped
- Don't need to worry about nginx timeouts
- Less risk that we end up storing large files twice on disk
There might be larger issues about the story you want to tell with this software, so I won't jump into this.
- I've made some progress with the approach of having a shared directory between the host and the container, but it adds a lot of superficial complexity: The user needs to keep track of the path on localhost, and in the container, and if one is confused for the other it will be hard to debug.
- I wonder if we don't want to keep URLs as the way files are specified. It avoids all these problems of trying to set up a back door in the container. If someone does really want to work with local files, maybe that should be considered the weird case, and the thing to do is bring up a one-line server for the files?
Currently giving a URL. How do we upload a local file? Can a volume to mount be specified at run time? or pipe? or rely on the use to know where the mounted dirs are?