Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug when using S3 compatible (not amazon) services #36

Open
awensaunders opened this issue Oct 15, 2020 · 2 comments
Open

Bug when using S3 compatible (not amazon) services #36

awensaunders opened this issue Oct 15, 2020 · 2 comments

Comments

@awensaunders
Copy link
Contributor

I use Minio in my local development environment to support developing on attachments. It doesn't work properly right now, because all the URLs that courier passes to rapidpro are wrong, pointing to Amazon S3 rather than my local minio environment.

var s3BucketURL = "https://%s.s3.amazonaws.com%s"
is hardcoded to amazon's URL. If it pulled from the config instead, it would be portable to various S3 compatible services.

I could make a PR if you want.

@rowanseymour
Copy link
Member

Sure, so passed in via S3Options but defaults to that existing AWS URL?

@awensaunders
Copy link
Contributor Author

That would be the behaviour I’d expect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants