Where's the documentation? I just see pricing and modals trying to get me to sign up.
Show HN: File0 – An easier way to manage files in serverless apps
41–50 of 158 posts
Re: Show HN: File0 – An easier way to manage files in serverless apps
#42If you don't need all of this, rent a VM somewhere, put a webserver on it (or use the static file support of your framework) and serve files from a directory on local storage. That's still possible and easy to do.
You do need to consider backups, you don't get high availability or anything like that and you're limited to the amount of storage you can attach to the VM. So it's not the same as S3 at all, but depending on your needs it is an entirely valid solution.
Serving files is a large space and people do very different things there. No single solution will fit all use cases and still remain simple.
Re: Show HN: File0 – An easier way to manage files in serverless apps
#43These comparisons are really unfair. For example there's no reason you have to use a bucket policy in the sdk (I've never). Unless it's S3 compatible it's going to be a gargantuan task to make this successful as _everything_ uses the S3 API.
Perhaps, but AWS certainly doesn't do a very good job of highlighting the most simple way to use it.
This is the user guide: https://docs.aws.amazon.com/AmazonS3/latest/userguide/Welcom...
Re: Show HN: File0 – An easier way to manage files in serverless apps
#44looking at the code side by side example: FILE0 does not provide authentication!? Everybody can upload files?
Guessing it reads some credentials out of environment variables. The client side example shows the server issuing a token so I guess it's only the server that has/needs the credentials.
Yeah, reading that example looks like it's basically signed URLs, and you define the permissions by deciding who can receive a signed URL on your server. Not a big deal for my use cases.
Re: Show HN: File0 – An easier way to manage files in serverless apps
#45The good thing about S3 is the API is stable this s bunch of clones have popped up, or at least workalikes.
100% legit concern. Obviously I can't sit here and say that my new crappy product is as stable as S3. But I can say that most parts are just a thin layer on top of R2. Obviously at the begining I expect bugs and disruption, but the product is simple enough to get it right quickly.
Re: Show HN: File0 – An easier way to manage files in serverless apps
#46[dead]
Re: Show HN: File0 – An easier way to manage files in serverless apps
#47Maybe I'm not a target customer of yours but I couldn't use this for now since I need to region lock to EU, which R2 has recently provided.
That said my honest thoughts are that for my company's simple use case, I set it up once in 15 mins and never really thought about it again, but I can see how someone who hasn't done it before would love this kind of DX.
Re: Show HN: File0 – An easier way to manage files in serverless apps
#48I like the part where you bulked up the S3 part unnecessarily and hid the extra stuff you needed for yours that S3 doesn’t need.
Sorry, but your code examples are a flat out lie.
Re: Show HN: File0 – An easier way to manage files in serverless apps
#49Nice! This looks pretty well thought out so maybe you have considered this already, but you should sort out how you want to handle your local laws surrounding hosting files and your culpability.
You will pretty quickly get nefarious and copyrighted material hosted on your servers, you will be asked by law enforcement for access and you will get DCMA take down requests, and scary sounding emails from lawyers.
Just engage a good lawyer, and check for any requirements local laws require you to fulfill pre-emptively.
Re: Show HN: File0 – An easier way to manage files in serverless apps
#50But you don't need to master bucket policies, ACL, CORS, multi part uploads, content headers, CDN, or pre-signed URLs for what this is doing. There's a bit more boilerplate to set everything to the "I don't care whatever" settings, but that's because the "I don't care whatever" approach is usually not what you want for anything serious.
I'm not sure how to use this from my Java or Rust projects. I also don't see any API docs so I don't know how to write a wrapper. I guess it's a project for and by Javascript developers.
I can't find anything about egress limits, file size limits, how incomplete transfers are handled, in what country the data is stored, and what happens when you try to create a file that already exists. Maybe that info is behind the login wall?