# Stylesheet cache in multi-server setup

**URL:** <https://meta.discourse.org/t/stylesheet-cache-in-multi-server-setup/24820>\
**Category:** Self-hosting\
**Tags:** hosting\
**Created:** [February 4, 2015, 8:41pm UTC](https://meta.discourse.org/t/stylesheet-cache-in-multi-server-setup/24820 "2015-02-04T20:41:41Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![pda](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pda/32/115583_2.png) [@pda](https://meta.discourse.org/u/pda)\
**Post date:** [February 4, 2015, 11:36pm UTC](https://meta.discourse.org/t/stylesheet-cache-in-multi-server-setup/24820/6 "2015-02-04T23:36:03Z")

</div>

It would be great to see this resolved in Discourse itself.

Eliminating ad-hoc local filesystem writes in favor of persisting to well-defined backing services along the lines of [The Twelve-Factor App](http://12factor.net/backing-services) would allowing easier deployments and horizontal scaling across different platforms. AWS Elastic Beanstalk may be a little less common, but the ability to run on Heroku seems a good litmus test for the deployability of an app.

Also, depending on this single local filesystem seems to be throwing out much of the benefit of the docker-by-default approach that I’ve been impressed Discourse is taking.

Given Discourse already depends on Redis, that seems like a decent candidate for storing runtime-rendered stylesheets. Or since S3 is already supported for uploads, that would be another option that doesn’t introduce new dependencies.

---

_[View the full topic](https://meta.discourse.org/t/stylesheet-cache-in-multi-server-setup/24820)._