We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
For some reason s3rver omits the first 5 letters of the bucket name.
Im starting s3 with s3rver -d ../data/s3rver -a 0.0.0.0 and when i try to uppload something to say the bucket printer the log output will say:
s3rver -d ../data/s3rver -a 0.0.0.0
printer
info: er 404 1ms -
when it should output info: printer 404 1ms -
info: printer 404 1ms -
The issue appears after updating from 1.0.3 to 3.5.0.
The text was updated successfully, but these errors were encountered:
@TheGrandmother I can't reproduce this. Here are the steps I took:
~/tmp6
cd
npm i s3rver
npx s3rver -d data/s3rver -a 0.0.0.0
aws s3 --endpoint=http://0.0.0.0:4568 mb s3://printer
aws s3 --endpoint=http://0.0.0.0:4568 cp Hello.txt s3://printer/Hello.txt
The output of the original terminal window is:
charliefish@Charlies-MacBook-Pro tmp6 % npx s3rver -d data/s3rver -a 0.0.0.0 S3rver listening on 0.0.0.0:4568 info: Created new bucket "printer" successfully info: PUT /printer 200 4ms 0b info: Stored object "Hello.txt" in bucket "printer" successfully info: PUT /printer/Hello.txt 200 9ms 0b
Not sure why you are getting a 404 error.
Can you please provide more detail about the exact steps you are taking to produce this error?
Sorry, something went wrong.
No branches or pull requests
For some reason s3rver omits the first 5 letters of the bucket name.
Im starting s3 with
s3rver -d ../data/s3rver -a 0.0.0.0
and when i try to uppload something to say the bucketprinter
the log output will say:when it should output
info: printer 404 1ms -
The issue appears after updating from 1.0.3 to 3.5.0.
The text was updated successfully, but these errors were encountered: