fenos

8 ms·

1. 1.▲
   by fenos 2y ago

   This is indeed at the very top of the list :)
2. 2.▲
   by fenos 2y ago

   We don’t support static website hosting just yet - might happen in the future :)
3. 3.▲
   by fenos 2y ago

   That is also a common pattern I agree, both ways are fine if the upload server is optimised accordingly :)
4. 4.▲
   by fenos 2y ago

   Our S3 Driver is compatible with any S3 Compatible object Storage so you don’t have to write one :)
5. 5.▲
   by fenos 2y ago

   Yes indeed! I would call it S3 on steroids! Currently, it happens to be S3 to S3, but you could write an adapter, let's say GoogleCloudStorage and it will become S3 -> GoogleCloudStorage, or any other type of underline Storage. Add
6. 6.▲
   by fenos 2y ago

   Yes, I agree! Although I should have specified that we support signed URL https://supabase.com/docs/reference/javascript/storage-from-... just not in the S3 protocol just yet :)
7. 7.▲
   by fenos 2y ago

   Thanks for asking this, we do not support signed URLs just yet, but it will be added in the next iteration
8. 8.▲
   by fenos 2y ago

   You can think of the Storage product as an upload server that sits in front of S3. Generally, you would want to place an upload server to accept uploads from your customers, that is because you want to do some sort of file validation, acces
9. 9.▲
   by fenos 2y ago

   Yes, absolutely! You can download files as streams and make use of Range requests too. The good news is that the Standard API is also supporting stream!
10. 10.▲
    by fenos 2y ago

    We do not store the files in Postgres, the files are stored in a managed S3 bucket. We store the metadata of the objects and buckets in Postgres so that you can easily query it with SQL. You can also implement access control with RLS to all
11. 11.▲
    by fenos 2y ago

    Yes, both can be fine :) after all, a Protocol can be interpreted as a Standardised API which the client and server interact with, it can be low-level or high-level. I hope you like the addition and we have the implementation all open-sourc
12. 12.▲
    The Million-Dollar Development Team(medium.com)

    1 points by fenos 4y ago|0 comments
13. 13.▲
    by fenos 8y ago

    Fantastic! I've never had a chance on launching the app on windows, I'm glad it worked! I think you are running the dev mode, that's why the Chrome dev tools appeared :) The import paths feature will be released soon so stay
14. 14.▲
    by fenos 8y ago

    Thanks, I’m glad you like it! Yes, TLS will arrive very soon. Reflection too but it will take slightly longer. Request chain will follow along! I haven’t thought about recording and replay. That is a great addition to the editor once we sup
15. 15.▲
    by fenos 8y ago

    Wow! Those two features will be certainly a good addition to the client! I’ll be adding them to the list
16. 16.▲
    by fenos 8y ago

    Hi! Creator of BloomRPC here. Thanks for the warming welcoming of the client! I’m glad to see lots of positive feedbacks. The client aim to give the best developer experience possible on your day to day usage of GRPC services. We are using