I have a weird issue where my stack fails if I give s3ClientConfig.endpoint a docker container to resolve e.g: http://minio:9000. If I give it the IP address, it works fine.
This is an issue because I’m using docker-compose to spin up the whole stack. I pass the minioS3 endpoint into my app as an environment variable and therefor the IP address can change.
I’m not sure why you want to pass endpoint. From the docs:
The fully qualified endpoint of the webservice. This is only for using a custom endpoint (for example, when using a local version of S3).Endpoint transformations such as S3 applying a bucket to the hostname are still applicable to this custom endpoint — docs
If you are not using a local version of S3, you probably don’t want this.
Hi, Thanks for getting back.
I am using a local version of s3. I spin up an instance of minIO in my docker-compose file to store the uploads.
Alright thanks for clarifying. In that case I can’t really help you. s3ClientConfig is passed directly to the AWS SDK so whatever happens there is outside of the control of tus.
cool, thanks. it was worth a shot!