# Purpose of the Discourse shared volume in a high availability setup

**URL:** <https://meta.discourse.org/t/purpose-of-the-discourse-shared-volume-in-a-high-availability-setup/113399>\
**Category:** Self-hosting\
**Tags:** hosting\
**Created:** [4월 4, 2019, 12:47오전 UTC](https://meta.discourse.org/t/purpose-of-the-discourse-shared-volume-in-a-high-availability-setup/113399 "2019-04-04T00:47:49Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [4월 4, 2019, 12:52오전 UTC](https://meta.discourse.org/t/purpose-of-the-discourse-shared-volume-in-a-high-availability-setup/113399/2 "2019-04-04T00:52:08Z")

</div>

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.

---

_[View the full topic](https://meta.discourse.org/t/purpose-of-the-discourse-shared-volume-in-a-high-availability-setup/113399)._