@robertgendler commented on GitHub:
Since opening this issue and pull request we had 2 thoughts on how to handle the check 1.
if sshd -T 2> /dev/null; then
....check...
else
...could…
@jtagcat commented on GitHub:
Yes, but I'm also using my self-hosted instance of it.
@JackDallas commented on GitHub:
So Digitalocean don't let you set a bucket wide policy it has to be set per item and items are private by default so you have to include the ACL policiy when you…
@paolafrancesca commented on GitHub:
@JackDallas sorry but it is still not clear
where do you set the base url? as --s3-endpoint to transfer.sh?
what is exactly not working?
why the item…
@paolafrancesca commented on GitHub:
@jtagcat the version hostend on https://transfer.sh and the version in the repo if you self-host are different, so please give more details.
- what version…
@JackDallas commented on GitHub:
ohhhh, So I set the base url to be the CDN provided with the bucket for faster access:
https://bucketname.region.digitaloceanspaces.com
So the link…
@paolafrancesca commented on GitHub:
are you referring to the service hosted at https://transfer.sh?
@jtagcat commented on GitHub:
- No idea where to check that.
dutchcoders/transfer.sh:lateston docker. - the feature does not exist
@paolafrancesca commented on GitHub:
@JackDallas can you explain in more details? transfer.sh doesn't create the bucket it writes into. why don't you just create it as public?
@paolafrancesca commented on GitHub:
@JackDallas but if the items are created private by default with the aws credentials of transfer.sh I expect that after the same client with the same…
@paolafrancesca commented on GitHub:
@JackDallas any answer from them to the ticket?
@paolafrancesca commented on GitHub:
@JackDallas now it is clear there is a question on digitalocean community forum about this issue: https://www.digitalocean.com/community/questions/how-to-se…
@paolafrancesca commented on GitHub:
@JackDallas is this still an issue?
@JackDallas commented on GitHub:
I'll open a ticket now to be sure!
I tried put-bucket-acl like the person in that ticket did but no luck, and searched all the docs
@Tribruin commented on GitHub:
Yes, I just checked and confirmed that user folders are now being set to the expected permissions 700.
Thanks.
@brodjieski commented on GitHub:
@Tribruin Let us know if the fix corrects the behavior you were seeing.
Thanks!
@JackDallas commented on GitHub:
Really sorry for the delay, the world went a bit crazy and dragged me with it, it seems this is something that can be done on digital ocean it just isn't easy,…
@JackDallas commented on GitHub:
Sorry let me re-phrase
Digital ocean provides a S3 service with built in CDN, so the bucket address is <bucketname>.<region>.digitaloceanspaces.com but the…