-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Allow use of S3-compatible storage buckets (e.g. Minio, Wasabi, etc.) #139
Comments
Currently there are different "providers" for uploading media. These satisfy I think we could add Minio to start with. Will add this to my TODO 👍 |
awesome! glad to see it being prioritized. let me know if you need any assistance. from quickly gandering at the code it would be as simple as allowing the endpoint for the amazon s3 url to be custom set as an environment variable. don't think you would need to use the Minio SDK, since it should be compatible with all s3 clients. |
Ah that makes it easier. Will try it out with Minio playground. |
hi @mr-karan were you able to get this working with the playground? if you need a dev instance, happy to provide u with one. |
@eddiewang I was able to upload it by simply changing the endpoint. The |
@mr-karan cool! Was the policy on the bucket set correctly? Assuming we need a public bucket using ‘mc policy set download /’ should do the trick. |
Hi! What is about this feature? There are no option in settings to change the host |
Ah, this isn't available on the settings UI in the current version. Will make it pluggable in the next release. |
#231 is an attempt to add webdav. |
@knadh @mr-karan so can I just confirm that, despite this ticket being closed, there still isn't the possibility to add a custom s3-compatible provider in listmonk? |
Thanks for bringing this up @c-nv-s. This was missed. Will add the backend URL as a configurable field on the S3 settings UI in the upcoming version. |
Are there any plans to extend the S3 storage method to allow for a custom S3 endpoint url?
This would allow third-party S3-compatible storage systems to work in tadem with listmonk. This is especially ideal if for self-hosted environments.
The text was updated successfully, but these errors were encountered: