21–30 of 158 posts
This seems like a great idea. I've come to think the UX requirements of enterprise and indie dev / start up customers are fundamentally incompatible in the cloud. As an enterprise I want to be able to set restrictions at the org, project, team and resource level for various compliance rules. And I want these rules to be restrictive by default (e.g block public access). However as an individual developer the mere exis…
Standard S3 is $.02/GB, this is $.12/GB so 6x the price. You don't pay data transfer with this solution at least. Quick alternative: #!/bin/bash if [ "$#" -ne 2 ]; then echo "Usage: $0 " exit 1 fi FILE_TO_UPLOAD=$1 S3_BUCKET=$2 S3_OBJECT_NAME=$(basename "$FILE_TO_UPLOAD") aws s3 cp "$FILE_TO_UPLOAD" "s3://$S3_BUCKET/$S3_OBJECT_NAME" --acl public-read if [ $? -eq 0 ]; then echo "File uploaded successfully." PUBLIC_URL…
Standard S3 is $.02/GB, this is $.12/GB so 6x the price. You don't pay data transfer with this solution at least. Quick alternative: #!/bin/bash if [ "$#" -ne 2 ]; then echo "Usage: $0 " exit 1 fi FILE_TO_UPLOAD=$1 S3_BUCKET=$2 S3_OBJECT_NAME=$(basename "$FILE_TO_UPLOAD") aws s3 cp "$FILE_TO_UPLOAD" "s3://$S3_BUCKET/$S3_OBJECT_NAME" --acl public-read if [ $? -eq 0 ]; then echo "File uploaded successfully." PUBLIC_URL…
It suffers the usual effect as seen in eg. Wayland. You think the problem is simple and make a new protocol that's simple. Then you find complexity in the problem and solve it with complexity in the solution. Then your protocol becomes as complex as the one you're replacing. There are reasons S3 does all these things. ACLs, for example? How do you control who can access a file you uploaded? Also, it costs about 20 ti…
If you need granular control, you can use S3. If you need the cheapest option out there you can use Backblaze. If your application is bandwidth heavy, you can use R2. If you're a busy indie hacker who just want to be up an running with file storage under 5 mins and forget the whole thing even exists, you can use FILE0. S3 is stuffed with features for a reason. It's the backbone of the internet so it needs to cover 10…
Willing to try wasabi next time.
I am old enough that I still remember people including myself being perplexed why s3 didn't ship with an FTP adapter. They FINALLY added the option in 2020, 14 years late. I do think the storage "space" could use some disruption. I use s3 every day at work, and my general feeling is that the entire permission system is more complicated than 99% of apps actually need, to the point of being dangerous; I think the compl…
Perhaps arsed rather than asked
I am old enough that I still remember people including myself being perplexed why s3 didn't ship with an FTP adapter. They FINALLY added the option in 2020, 14 years late. I do think the storage "space" could use some disruption. I use s3 every day at work, and my general feeling is that the entire permission system is more complicated than 99% of apps actually need, to the point of being dangerous; I think the compl…
And then policies are an attempt (I think) at simplifying permissions to a bucket with one declaration, but in practice what I see are people copy-pasting decades-old (really!) policies from other projects because most of us just need to get a private file store up and running.
Platform exhaustion - I have to know so much about AWS to not make a huge mistake that it takes away from my actual product development work that my company expects out of me.