Hi! I’m wondering what the purpose of the shared volume is in a Discourse deployment? For context, we have Discourse up and running in a Kubernetes cluster (in GKE), but we’d like to scale out the number of instances of our deployment to make it more highly available. All instances would obviously …

The shared volume is there as a value add you can get away without it. In a typical “uploads are on AWS”, PG / Redis somewhere central setup you will only use it for Rails/Unicorn/NGINX etc logs. You would then ship them somewhere central with some log aggregation service.

Perfect, thanks @sam ! Just wanted to check that there weren’t going to be issues with uploads going to one host, and then a request hits another host and isn’t available due to it running in a separate container with a separate mount. Sounds like we’ll be ok here :+1:.

Purpose of the Discourse shared volume in a high availability setup

Product Support Self-hosting

sam (Sam Saffron) April 4, 2019, 1:43am 4

Note, It will be an issue unless you use our s3 uploads provider

Topic		Replies	Views
Sharing shared volumes Product Support	10	1171	May 22, 2018
Using multiple containers - what needs to be shared? Self-hosting	1	990	March 3, 2021
Moving discourse instance to a new server Self-hosting	6	333	August 11, 2025
How to scale discourse? Self-hosting hosting	4	4325	February 9, 2015
Making use of added storage volumes Self-hosting hosting	12	5514	August 25, 2017

Purpose of the Discourse shared volume in a high availability setup

Related topics