# Inicializando uma imagem do Docker do Discourse com a URL do SSO como variável de ambiente

**URL:** <https://meta.discourse.org/t/bootstrapping-a-discourse-docker-image-with-sso-url-as-environment-variable/85107>\
**Category:** SSO\
**Created:** [11 Abril , 2018 19:05 UTC](https://meta.discourse.org/t/bootstrapping-a-discourse-docker-image-with-sso-url-as-environment-variable/85107 "2018-04-11T19:05:11Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [24 Abril , 2018 20:15 UTC](https://meta.discourse.org/t/bootstrapping-a-discourse-docker-image-with-sso-url-as-environment-variable/85107/7 "2018-04-24T20:15:13Z")

</div>

Hi, @shahidmir. I just got around to paying closer attention to this.

Yes, my read of Sam’s message is that you’d need to submit a PR that adds `shadowed_by_global: true` to the SSO field(s) that you want to set with an environment variable and that he’d likely accept it. That seems like the cleanest solution to your problem.

My uploader would also be a solution, but the trick with it is that you need the API key, which is something of a bother to set/get.

If you have a github account, you can simply visit the `site_settings.yml` link above, click the pencil icon, edit the file, save, and submit a PR. Spaces are very, very important in `yml` files, so it would be safest to copy-paste another “shadowed\_by\_global: true” line so that you don’t inadvertently enter a tab or the wrong number of spaces.

---

_[View the full topic](https://meta.discourse.org/t/bootstrapping-a-discourse-docker-image-with-sso-url-as-environment-variable/85107)._
