The discussion revolves around bypassing Discourse’s local storage to directly upload files to S3. amoncadot initiated the conversation, seeking a way to upload images directly to S3 without storing them locally first. However, schleifer stated that this would require significant rework of the upload handling. sam expressed interest in implementing direct S3 uploads using a ticket system but noted that it’s not a priority in the next few months. Meanwhile, supermathie announced that a project to improve file uploads in Discourse is now active, potentially addressing this issue.
Hello,
We would like our users to upload files (images specifically but hopefully video later), however since we are running Discourse using Docker, there’s no point in Discourse storing the files locally before the files are sent to S3.
Is there anyway we can bypass Discourse’s local storage and just fire the images off to S3 straight away when someone uploads a file?
Thanks,
Amoncadot
No. The upload handling would have to be significantly reworked to go straight to S3.
Hi Andrew,
Great, thanks for your reply!
I would like us to get to direct s3 uploads using some sort of ticket system. The big problem though is that this would only be useful for attachments, it is critical all images go via the app.
For images we always do a bit of magic first, ensuring giant PNGs turn into JPEGS and such.
I don’t see us working on this in the next few months at least.
This is now an active project: