-
-
Notifications
You must be signed in to change notification settings - Fork 13
Open
Labels
unnecessary bloat but will accept prout of scope for the project but external submissions will be acceptedout of scope for the project but external submissions will be accepted
Description
Is your feature request related to a problem? Please describe.
Forgive me if this has already been suggested, I've taken a search through the issues but nothing came up.
The ability to set an upload destination to an S3 Provider, ideally abstract enough to support different providers like Digital Ocean Spaces, S3, Cloudflare R2, Backblaze (selfhosted s3) etc.
Technically with what is provided via your json spec, this might nearly be possible but one of the complications is the signature that needs to be generated from the data you're about to upload. In-code this is relatively trivial but via the JSON, I couldn't quite figure it out.
Describe the solution you'd like
- Ability to define your custom provider as a S3 provider
- Support url rewriting like you do in the JSON where you can take different parts to use as a replacement pattern.
Describe alternatives you've considered
- Attempted to use the
jsonproviders exampled
iSnakeBuzz and thehairy
Metadata
Metadata
Assignees
Labels
unnecessary bloat but will accept prout of scope for the project but external submissions will be acceptedout of scope for the project but external submissions will be accepted