# Redis template no longer works for separate data container

**URL:** <https://meta.discourse.org/t/redis-template-no-longer-works-for-separate-data-container/109704>\
**Category:** Bug\
**Created:** [February 20, 2019, 10:37pm UTC](https://meta.discourse.org/t/redis-template-no-longer-works-for-separate-data-container/109704 "2019-02-20T22:37:35Z")\
**Posts on this page:** 1\
**Showing post:** 7

<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:** [February 21, 2019, 3:15am UTC](https://meta.discourse.org/t/redis-template-no-longer-works-for-separate-data-container/109704/7 "2019-02-21T03:15:09Z")

</div>

> [@pfaffman](#):
>
> I may not understand, but my take is that they changed the default upstream.

Sure which is fine, but we can ship our own default 😊…

> <https://github.com/discourse/discourse_docker/commit/281190efb367298f4134672ff25082a5a74fba9f>
>
> We do not require protected mode in redis cause it runs in a container
> and is de…fault protected.
> 
> Protected mode breaks running our template in a multi container setup or
> certain users exposting redis from the container if they wish

---

_[View the full topic](https://meta.discourse.org/t/redis-template-no-longer-works-for-separate-data-container/109704)._