@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?
@paolafrancesca commented on GitHub:
@jtagcat your request is not feasable: to allow you to Ctrl+L Ctrl+C the page should redirect to the url of the file uploaded, but since you can upload…
@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?
@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…
@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,…