-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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 File Upload component should work with other S3-compatible services, not just AWS #5587
Comments
Please move away from MinIO.Please Note: Minio - has changed license terms. No longer opensource or free. "Designed for developers who are building open source applications in compliance with the GNU AGPL v3 license and are able to support themselves. It is fully featured. If you distribute, host or create derivative works of the MinIO software over the network, the GNU AGPL v3 license requires that you also distribute the complete, corresponding source code of the combined work under the same GNU AGPL v3 license. This requirement applies whether or not you modified MinIO." If you customize budibase and add a form; because bb uses minio, you have to release your org bb-custom-code public! Whether or not you modified MinIO. |
Backblaze support would be really great. It's S3 compatible. |
This issue has been automatically marked as stale because it has not had recent activity. |
+1 for this I found a bit of a workaround here, it seems to use the same AWS sdk that budibase uses and it works! The only downsides are that - 1. There's no easy way to retrieve the filename of what was uploaded and 2. Kind of a big one... all your S3 keys are visible in plain text in source soooooo |
This issue has been automatically marked as stale because it has not had recent activity. |
Any updates on this ? |
Discussed in #5459
Originally posted by daawaan April 17, 2022
Hello, I've been trying to use the S3 File Upload component since the 20MB file upload limit for attachments is too small for our use case which is explained further in #5457. Unfortunately, the S3 component isn't showing any of the S3 datasources in the dropdown for the component which I've already issued in #5454. We're using digitalocean spaces in our case and I was wondering if our datasource wasn't showing up because it isn't from AWS? Its also stated here in #4030 the first pull request for the S3 File Upload component that
The text was updated successfully, but these errors were encountered: