# Which settings can be configured without a container rebuild?

**URL:** <https://meta.discourse.org/t/which-settings-can-be-configured-without-a-container-rebuild/116266>\
**Category:** Self-hosting\
**Tags:** hosting\
**Created:** [April 29, 2019, 5:46pm UTC](https://meta.discourse.org/t/which-settings-can-be-configured-without-a-container-rebuild/116266 "2019-04-29T17:46:43Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![russellwstanley](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/russellwstanley/32/156979_2.png) [@russellwstanley](https://meta.discourse.org/u/russellwstanley)\
**Post date:** [April 29, 2019, 5:46pm UTC](https://meta.discourse.org/t/which-settings-can-be-configured-without-a-container-rebuild/116266/1 "2019-04-29T17:46:43Z")

</div>

Hi

Quick question about the possibility of deploying the same discourse image to multiple environments (staging, beta, production etc).

I’d like to build the discourse image once in my CI/CD pipeline, push that image to a repository, and have the exact same discourse image running in all environments. I’d like the differences between environments (hostname etc) to be represented in environment variables or configuration files that are external to the container. With discourse my experience is that it is not entirely obvious which settings are baked into an image and which are safe to configure by changing the yaml without a rebuild.

Is there a list of the variables that can safely be configured in each environment without a container rebuild somewhere?

---

_[View the full topic](https://meta.discourse.org/t/which-settings-can-be-configured-without-a-container-rebuild/116266)._
