Solving a caching issue of minio + small improvements when creating users

[fversaci]

• There was an issue when uploading large files with POST to the minio server: without the "filename" field data is considered small and cached in memory, with a hard limit of 16 MB. I've added the filename" field to force minio to cache data to disk during the upload, thus bypassing the 16 BM limit.
• I've also adopted the standard minio server in the docker-compose, which now works fine.
• Small changes/fix when creating users

[shodr]

Hi, fversaci
I was trying to implement regular minio, with your changes, but I get an error "There were headers present in the request which were not signed", I get this error whichever version of minio docker image I use (latest or the ones form the date you posted your solution. Tried modifying function "getDownloadDetails", or to point directly at minio server (without redirect to 8082), but cannot get around the error. I can generate download links through mino browser or AWS cli in app-zotero, but not through zotero client.
Do you, anybody else know a solution. (I am behind corporate proxy if its relevant). I believe the issue ist with the header X-Amz-Content-Sha256: which is signed as an empty string (hash: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855), but cannot get the SDK to ignore it when generating link).
tnx.
tnx