Skip to content
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 Uploading provider #113

Open
MichaelHillcox opened this issue Feb 17, 2025 · 0 comments
Open

S3 Uploading provider #113

MichaelHillcox opened this issue Feb 17, 2025 · 0 comments
Labels
unnecessary bloat but will accept pr out of scope for the project but external submissions will be accepted

Comments

@MichaelHillcox
Copy link

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 B2, 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 json providers exampled
@castdrian castdrian added the unnecessary bloat but will accept pr out of scope for the project but external submissions will be accepted label Feb 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
unnecessary bloat but will accept pr out of scope for the project but external submissions will be accepted
Projects
None yet
Development

No branches or pull requests

2 participants