# Minha instalação está 16.359 commits atrás! Alguma dica?

**URL:** https://meta.discourse.org/t/my-install-is-16-359-commits-behind-advice/354327
**Category:** Self-hosting
**Created:** [25 Fevereiro , 2025 06:53 UTC](https://meta.discourse.org/t/my-install-is-16-359-commits-behind-advice/354327 "2025-02-25T06:53:27Z")
**Posts on this page:** 1
**Showing post:** 13

<div class="post-metadata">

### Author: ![trusktr](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/trusktr/32/116841_2.png) [@trusktr](https://meta.discourse.org/u/trusktr)
#### Post date: [17 Março , 2025 01:11 UTC](https://meta.discourse.org/t/my-install-is-16-359-commits-behind-advice/354327/13 "2025-03-17T01:11:09Z")

</div>

Eu atualmente tenho isto no meu app.yml de anos atrás:

```plaintext
  # TODO (joe) remover esta linha assim que o Discourse corrigir o problema associado
  # Ver https://meta.discourse.org/t/upgrade-rebuilds-fail-due-to-maxmind-db-eol/137387/2
  DISCOURSE_REFRESH_MAXMIND_DB_DURING_PRECOMPILE_DAYS: 30

```

Ligando para:

> [@Upgrade / Rebuilds Fail due to MaxMind DB EOL](https://meta.discourse.org/t/upgrade-rebuilds-fail-due-to-maxmind-db-eol/137387):
>
> Guys, Hope somebody can help here. Ive not had a problem for over 12 months with upgrades to my forum that is running in a docker container on EC2 Ive tried: launcher cleanup but no issues with disk space latest git pull multiple app rebuilds Even tried a discourse-setup and was going to try a DB restore frowningServer reboot apt-get update; apt-get upgrade Here is the tail of the log Done compressing all JS files : 88.88 secs rake aborted! SocketError: Failed to open TCP connection to…

Posso apagar isso com a nova instância? Ou preciso fazer alguma coisa? Presumo que isso foi resolvido há muito tempo e posso evitar incluir esta configuração no app.yml?

---

_[View the full topic](https://meta.discourse.org/t/my-install-is-16-359-commits-behind-advice/354327)._