MyS3Browser icon indicating copy to clipboard operation
MyS3Browser copied to clipboard

Feature Request: Allow Option of Endpoint-URL

Open krismeister opened this issue 5 years ago • 2 comments

Currently there is no option to allow browsing with the --endpoint-url option.

The feature allows you to point to a different URL than amazon for instance if you are running S3MOCK https://github.com/adobe/S3Mock .

# run docker s3Mock locally
docker run -p 9090:9090 -t adobe/s3mock

# create a bucket
aws --endpoint-url=http://localhost:9090 s3 mb s3://testing

#push a file
aws --endpoint-url=http://localhost:9090 s3 cp test.txt s3://testing/test.txt

It would be convenient to allow this option in MyS3Browser .

krismeister avatar May 28 '20 20:05 krismeister

Big 👍 to this feature request. It would allow us to use the browser with Wasabi.

rabernat avatar Aug 28 '20 11:08 rabernat

I've tried to get the source code, but it is not buildable. Did you commit all the source code, @shishirsharma ?

trinh.pham@MyMac MyS3Browser % npm run build -- -prod

> [email protected] build /Volumes/Data/Projects/MyS3Browser
> ng build "-prod"

Date: 2020-09-24T10:28:33.158Z                                                     
Hash: 4c86756d5a83a076c04c
Time: 6851ms
chunk {0} styles.d41d8cd98f00b204e980.bundle.css (styles) 0 bytes {3} [initial] [rendered]
chunk {1} polyfills.3bc34265385d52184eab.bundle.js (polyfills) 86 bytes {3} [initial] [rendered]
chunk {2} main.e402deade8b026b7d50e.bundle.js (main) 84 bytes [initial] [rendered]
chunk {3} inline.22b7623ed7c5ac6f9a35.bundle.js (inline) 1.45 kB [entry] [rendered]

ERROR in ng:///Volumes/Data/Projects/MyS3Browser/src/app/navbar-dropdown-credential-menu/navbar-dropdown-credential-menu.component.html (3,3): Property 'currentCredential' does not exist on type 'NavbarDropdownCredentialMenuComponent'.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] build: `ng build "-prod"`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/trinh.pham/.npm/_logs/2020-09-24T10_28_33_220Z-debug.log

trinhpham avatar Sep 24 '20 10:09 trinhpham