davidkarolyi

6 ms·

31.
by davidkarolyi 2y ago
Yeah you addressed the elephant in the room. Obviously it's a brand new product, with 0 reputation. As with every new product at the begining I expect bugs and disruptions, but IMO the product is simple enough to get it right quickly.
32.
by davidkarolyi 2y ago
This is on me. Right now all the instructions & setup guide & code snippets lives in your dashboard, appears after signup. You're not the first one pointing out the lack of public docs, and it's a legit need to take a look
33.
by davidkarolyi 2y ago
And thats fine! You should keep using R2. It's amazing. Obviously for experienced seniors who did this a million times, much easier to stick with S3/R2! Cheers
34.
by davidkarolyi 2y ago
What's your point exactly?
35.
by davidkarolyi 2y ago
Yeah more or less the comments are correct, but let me clarify! FILE0 is looking for an environment variable, that contains your API key. This is how you authenticate yourself from your backend. When you want to use client uploads you can u
36.
by davidkarolyi 2y ago
Interesting you mention this. That was the first approach. The problem comes when you want to introduce missing features to S3. Like tokens, or file filtering.
37.
by davidkarolyi 2y ago
No docs. In your dashboard there is a "Snippets" collection, which contains all information you need to use FILE0. It's kind of a code tutorial. If you find something fuzzy, let me know and I help you out.
38.
by davidkarolyi 2y ago
Yes, it is using R2 and CF workers.
39.
by davidkarolyi 2y ago
I disagree. Only an import statement is missing from both examples. Which parts is missing in your opinion?
40.
by davidkarolyi 2y ago
Yes. No egress fees. It's built on top of R2. they don't charge for network transer, so FILE0 neither. No! I believe if you look for S3 compatible storages you find much better options out there then FILE0. R2, Backbaze and others
41.
by davidkarolyi 2y ago
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 pro
42.
by davidkarolyi 2y ago
Good to hear! Initially I built it for myself without the intention to publish, but good to hear I'm not the only one has big-cloud provider fatigue.
43.
by davidkarolyi 2y ago
This was my catch phrase for years, and today I learned I used it wrong all the time.
44.
by davidkarolyi 2y ago
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
45.
Show HN: File0 – An easier way to manage files in serverless apps(file0.dev)
212 points by davidkarolyi 2y ago|154 comments
46.
Show HN: I made a platform to build background workflows via Node.js(turboq.dev)
1 points by davidkarolyi 2y ago|0 comments
47.
This is How to Overengineer Anything(levelup.gitconnected.com)
3 points by davidkarolyi 4y ago|0 comments