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

Use with s3 compatible storage #14

Open
snerdish opened this issue Jun 26, 2015 · 3 comments
Open

Use with s3 compatible storage #14

snerdish opened this issue Jun 26, 2015 · 3 comments

Comments

@snerdish
Copy link

My s3cmd config file specifies a local radosgw for s3 compatible storage, but s3-cli doesn't take note of this.

@BartVB
Copy link

BartVB commented Jun 16, 2016

Same problem here. This is probably because s3-cli doesn't pickup the host_base and 'host_bucket options from .s3cfg:
http://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/Endpoint.html
http://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/Config.html#s3BucketEndpoint-property

@deguich
Copy link

deguich commented Jan 12, 2018

Yes, I've got the same problem. I use a bad solution, I hardcoded the endpoint to my rados gateway in source code.

In s3-cli/cli.js line 90:

s3Options: {
      accessKeyId: accessKeyId,
      secretAccessKey: secretAccessKey,
      sslEnabled: !args.insecure,
      endpoint: 'myradosgw.org',
      region: args.region,
    },

I can dev and "pull request" the solution If andrewk is OK.

@ghost
Copy link

ghost commented Aug 25, 2018

Can this be pushed please? Being able to use compatible storage is important.
This fix still works and it would be great if the tool officially supports the endpoint input.

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

3 participants