# Migrar para S3 para problemas com Digital Ocean Spaces

**URL:** <https://meta.discourse.org/t/migrate-to-s3-for-digital-ocean-spaces-woes/109662>\
**Category:** Self-hosting\
**Tags:** s3\
**Created:** [Fevereiro 20, 2019, 3:54pm UTC](https://meta.discourse.org/t/migrate-to-s3-for-digital-ocean-spaces-woes/109662 "2019-02-20T15:54:27Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![tgxworld](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tgxworld/32/106117_2.png) [@tgxworld](https://meta.discourse.org/u/tgxworld)\
**Post date:** [Março 11, 2019, 6:32am UTC](https://meta.discourse.org/t/migrate-to-s3-for-digital-ocean-spaces-woes/109662/19 "2019-03-11T06:32:47Z")

</div>

This was a sneaky one…

[https://github.com/discourse/discourse/commit/d82876896eaf2ccd150ea9202003ed11742d2136](https://github.com/discourse/discourse/commit/d82876896eaf2ccd150ea9202003ed11742d2136)

If you’re on a docker based install, `GlobalSetting` uses the `FileProvider` which reads from `/var/www/discourse/config/discourse.conf`. That file is [only populated from the ENV once when the container is first started](https://github.com/discourse/discourse_docker/blob/024ebc4037b747d921433a45466e9fff45b0710c/templates/web.template.yml#L40-L49). As a result, running `DISCOURSE_S3_REGION rails console` will not have any effect on `GlobalSetting.s3_region` since it has not been added to `config/discourse.conf`.

---

_[View the full topic](https://meta.discourse.org/t/migrate-to-s3-for-digital-ocean-spaces-woes/109662)._