-
Notifications
You must be signed in to change notification settings - Fork 87
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
Can S3 really be used as a storage? #2803
Comments
Hello, We created a fork for flask-fs here for futher development. |
Hi @quaxsze, thanks for your comment. The fact that you're using GridFS might explain my troubles with S3. That said, nice to know that there's a fork of Will close this issue as this was more for discussion, thanks again. |
@quaxsze One additional question. Nevertheless the fork exists, it seems to be not used by udata yet. When is it planned to switch to it? |
Well we made the fork in the first place in order to upgrade |
Detailed Description
I've been playing around with
udata
and trying to connect multiple S3-compatible storages to it. I succeeded to certain extent but even reaching that stage already required some fixes both inudata
andflask-fs
.flask-fs
seems to have a nice idea of abstraction but it looks pretty immature when it comes to S3 support and the project itself is inactive, although has known issues.Multiple questions here:
flask-fs
dependency/create a fork? Contributing doesn't seem to be an option unfortunatelyContext
When I use
udata
, I want to have support for multiple storage types, so I could choose the one that works best for me.Possible Implementation
See questions.
Your Environment
N/A
The text was updated successfully, but these errors were encountered: