I really like having the option to easily decouple the app server from the asset storage.
If you pull out these S3 connectors, how hard will it be to build it back in using a plugin?
I do understand that for the vast majority of Discourse installs it's simpler to just stick everything together on a single box.
But as I think about migrating RockClimbing.com off our current setup, we've got 80+ gb of images, videos, etc across multiple apps, and these apps sometimes access the same files. For example, our climbing routes app, our photos app, and our forum currently can all easily access the same photo file.
My current plan is to break out each app into it's own Docker container, alongside our Discourse Docker instance, and use a single S3 bucket as the central file storage for our non-code assets across all apps, rather than try to get various apps to reach inside the Discourse Docker container on another server.
Or am I misunderstanding and pulling out the S3 connectors wouldn't affect this scenario? I don't understand what @sam means about when he talks about supporting origin pull cdn is better than supporting S3...
Or maybe there's some reason I'm unaware of why each app/docker container should have a separate file store? (more of a general web app architecture question than a discourse-specific question)