Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: File0 – An easier way to manage files in serverless apps

file0.dev

Post reply on HN
Print view View original

91–100 of 158 posts

Re: Show HN: File0 – An easier way to manage files in serverless apps

#91

Post by davidkarolyi »

jasonlotito wrote: post #87
davidkarolyi wrote: post #56

Earlier quoted context omitted.

I disagree. Only an import statement is missing from both examples. Which parts is missing in your opinion?

> Only an import statement is missing from both examples. import { S3Client, PutObjectCommand } from '@aws-sdk/client-s3'; Really? C'mon. It's YOUR examples on YOUR site. Regardless, that's not even what I'm worried about. The part where you need a key for this service and don't need any of that for S3. Sorry, but now that means I have to handle credentials with this service, which is something I like to avoid as muc…

I will kindly ignore the mental breakdown.

About the rest: For s3 you need to instantiate the client, and the only part you're correct about is that the client credentials can be also auto detected from env vars.

Let's boil the rest down: - For S3 you will need to add 2 env vars: AWS_ACCESS_KEY_ID, AWS_ACCESS_KEY_SECRET. In case you don't have other AWS keys in your env for other services this will be auto detected by the client. (Still needs to be instantiated), so you can cross off the 2 lines for creadentials.

- For FILE0 you need to add 1 env var: F0_SECRET_KEY. Then import the client which is autodetecting your env. ``` import {f0} from 'file0';

f0.set('myshit.png', myFile); ```

I'll let everyone be the judge of which one is simpler for them. And you should also use whichever you like more. I will sleep good at night either way and keep using file0.

Re: Show HN: File0 – An easier way to manage files in serverless apps

#93

Post by davidkarolyi »

anyfactor wrote: post #92

I could not find the docs. Does it offer a static storage URI for people to download stuff via a link? Can I update the contents of the storage URI without generating a new URI everytime?

There are no docs. Once you create an account you will have a setup guide and will have a useful snippets section in your dashboard that contains everything you need to know about file0.

Yes. By default all your files are private and only you can access them. To make a public url you can use f0.publish('filename'); This returns a static url that you can share with anyone, and they can download the file.

This url will stay valid until the file is deleted or unpublished via f0.unpublish('filename');

If you call publish again, it will generate a new public URL.

Re: Show HN: File0 – An easier way to manage files in serverless apps

#94

Post by jinushaun »

jeroenhd wrote: post #50

But 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…

I recently had to set up an S3 bucket and ran into all the issues the OP mentioned. I remembered when S3 was simple and just works. Now the default set up flow is advanced enterprise secure web scale.

Re: Show HN: File0 – An easier way to manage files in serverless apps

#96

Post by eksapsy »

chipdart wrote: post #58
jvans wrote: post #26

Earlier quoted context omitted.

This is classic feature bloat of a product that's been around for a while. Some customer wants a really niche feature so product adds a new option for it. It's just one new option so the experience isn't that different. Rinse and repeat hundreds of times and nobody stops the think of the cumulative effect on the 99% of customers who don't need those features.

> Rinse and repeat hundreds of times and nobody stops the think of the cumulative effect on the 99% of customers who don't need those features. Does it cost anything to not use features you do not need? Last time I checked, all the so-called niche features were stashed in hierarchical option lists, outside of the happy path. You need to purposely want to dig into, say, file access, bucket access metrics, storage stra…

Complexity without ease of use costs. S3 kind of forces you to use those features. If all you wanted was just a public/private access, you're forced to read into the complexity of S3's complex permission system.

So, to be fair, yes it costs to not use features you do not need in this case.

You literally pay by the hour to use S3, and you also pay the hours you spend trying to understand the permissions and modify settings, so it literally costs to not use the features you do not need in this case. I'm trying to make an argument, I'm not saying you pay much, but I answered your question, and you do pay, either by time, or money.

Re: Show HN: File0 – An easier way to manage files in serverless apps

#97

Post by SahAssar »

davidkarolyi wrote: post #79
jeroenhd wrote: post #50

But 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…

The webpage is a little bare-bones apologies. The setup instructions and tutorial appears when you create an account. At the moment the client package is only for js/ts devs. The package is based on HTTP api calls so it shouldn't be a huge issue porting it to other languages, but obv it's challenging without public HTTP specs. If you're into implementing a wrapper I'd be happy to assist and share those details. About…

> If the file already exists, it is overriden.

So any one of my users could overwrite or delete my other users files? Seems like this is not really thought through.

Re: Show HN: File0 – An easier way to manage files in serverless apps

#98

Post by ryanisnan »

SahAssar wrote: post #97
davidkarolyi wrote: post #79

Earlier quoted context omitted.

The webpage is a little bare-bones apologies. The setup instructions and tutorial appears when you create an account. At the moment the client package is only for js/ts devs. The package is based on HTTP api calls so it shouldn't be a huge issue porting it to other languages, but obv it's challenging without public HTTP specs. If you're into implementing a wrapper I'd be happy to assist and share those details. About…

> If the file already exists, it is overriden. So any one of my users could overwrite or delete my other users files? Seems like this is not really thought through.

But you... control the file names... You can overwrite contents in most other file systems easily.

Re: Show HN: File0 – An easier way to manage files in serverless apps

#100

Post by lbotos »

sosodev wrote: post #99

Why isn’t your pricing metered? Flat rate for storage generally feels scammy and the enterprise “contact us” really confirms that for me.

Not OP but scammy is a bit harsh here. I do agree, metered would be cool, but for v1 I'm not surprised to see the pricing as such.
Post reply on HN