I tried to configure Spliit with the S3 backend Garage. Unfortunately it doesn't just work out of the box. I had to fiddle a lot with our nginx setup (misuse the web endpoint of garage to get "anonymous" access to the actual file upon nginx request). It's working now ...
The most important thing to get things working were probably those two variables in the .env file.
AWS_REQUEST_CHECKSUM_CALCULATION=WHEN_REQUIRED
AWS_RESPONSE_CHECKSUM_VALIDATION=WHEN_REQUIRED
It's possible that other alternative S3 backends needs those too. After the 3.729.0 release of aws-sdk-js the checksum calculations and validations changed in client-s3 (which is used by next-s3-upload).
Probably this wouldn't be necessary, if Spliit would use a "private" S3 storage bucket and not a public one, something like this PR #499 which lets handle Spliit all the uploading and retreiving of the documents in the "background".
I tried to configure Spliit with the S3 backend Garage. Unfortunately it doesn't just work out of the box. I had to fiddle a lot with our nginx setup (misuse the web endpoint of garage to get "anonymous" access to the actual file upon nginx request). It's working now ...
The most important thing to get things working were probably those two variables in the
.envfile.It's possible that other alternative S3 backends needs those too. After the 3.729.0 release of
aws-sdk-jsthe checksum calculations and validations changed inclient-s3(which is used bynext-s3-upload).Probably this wouldn't be necessary, if Spliit would use a "private" S3 storage bucket and not a public one, something like this PR #499 which lets handle Spliit all the uploading and retreiving of the documents in the "background".