We need to disable /fileupload in our app while retaining the feature we have now. Is there a way to do that? It also needs to be private
Another option is to use our existing S3 and replace every custom uploader and the /fileupload API, but it’ll be time-consuming.
Hey Eugene,
Yeah, you can actually do that. Instead of using the /fileupload endpoint, you can handle file uploads through a backend workflow. Basically, the idea is to send the file (either as Base64 or multipart form) to your backend API workflow, then use the “Upload data as file” action to save it to your Bubble or S3 storage.
If privacy’s your main concern, you can also set up privacy rules so the file URLs are only visible to the right users.
I’ve done something similar before.
That doesn’t make the file itself private
Exactly. I need url to be private. Is there a way to do that via the backend?
This topic was automatically closed after 70 days. New replies are no longer allowed.
