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

Introduce @uppy/server-functions #5033

Open
2 tasks done
Murderlon opened this issue Mar 27, 2024 · 0 comments
Open
2 tasks done

Introduce @uppy/server-functions #5033

Murderlon opened this issue Mar 27, 2024 · 0 comments
Assignees
Labels

Comments

@Murderlon
Copy link
Member

Murderlon commented Mar 27, 2024

Initial checklist

  • I understand this is a feature request and questions should be posted in the Community Forum
  • I searched issues and couldn’t find anything (or linked relevant results below)

Problem

We strongly discourage using Companion just for S3 signing if aren't using Companion already. But when you need to implement it for you own backend, we require an embarrassing amount of almost 600 lines of complex code (client, server).

This issue is particularly about the server-side code.

Solution

Introduce @uppy/server-functions which exports functions for the S3 logic to be used inside a route handler. This would significantly reduce the burden to introduce S3 in your own backend with Uppy.

In the future I can imagine more things in this package for @uppy/xhr-upload. Things like server-side validation similar to UploadThing and generating a Transloadit signature.

Alternatives

Export a router which can be integrated in any Node.js framework. Take a look at how tus-node-server does this for inspiration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants