-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
S3 compatible providers #159
Comments
I would imagine you could just use any ABI compatible endpoint. We're a little late with the new release of firestorm. 2.0 revamps things a bit and loses some features (like file uploads out of the gate) but we will add them back (with the help of the community? :D) The current design makes it hard to use incrementally. In 2.0 you can use the data layer standalone (for instance to put your own UI on it). We're also releasing a graphql server for firestorm, as well as clients in each of Elm 0.19, Flutter, React Native, and Vue. I expect it to be announced in the first week of December. We intended for it to come out a month ago, but I had a conference talk to prepare for (my first keynote!) If you'd like to work on file uploads in 2.0 I'd be glad to pair on it as well. Additionally, 2.0 will support prometheus metric instrumentation. Unrelated entirely to this issue, but hey :) And for kicks it uses Ecto 3.0 and Phoenix 1.4. |
That seems like a huge update (including multiple front end frameworks is awesome). Thank you for continuing to work on this project! |
Wow, that sounds like a huge update! |
@Silentagony @ng-0, here are some updates: - Firestorm vue client: - Firestorm Flutter Client - Firestorm React Native |
I am no S3 user, but recently another Phoenix project I use (Pleroma) introduced the ability to use different s3-like providers, like wasabi (https://wasabi.com/s3-compatible-cloud-storage/). Is it already possible to use such ABI compatible endpoints, or is the current design hardwired to s3?
If it is hardwired, it would be a good feature to introduce the ability to use compatible providers.
The text was updated successfully, but these errors were encountered: