# Does web based updates replace rebuilding the container?

**URL:** <https://meta.discourse.org/t/does-web-based-updates-replace-rebuilding-the-container/102090>\
**Category:** Self-hosting\
**Created:** [November 15, 2018, 6:47am UTC](https://meta.discourse.org/t/does-web-based-updates-replace-rebuilding-the-container/102090 "2018-11-15T06:47:22Z")\
**Posts on this page:** 1\
**Showing post:** 14

<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:** [July 23, 2023, 6:15am UTC](https://meta.discourse.org/t/does-web-based-updates-replace-rebuilding-the-container/102090/14 "2023-07-23T06:15:31Z")

</div>

> [@dfriestedt](#):
>
> When upgrading, do I ever need to update the data container? If so, when?

When there is a change to postgres or redis. Knowing when this has happened is a matter of keeping track of things and is the reason that many people think that the two container setup is too hard. I have scripts that check postgres and redis versions and upgrade the data container if a change has been made. Those changed happen every year or two, though sub-base upgrades happen a bit more often. Generally if you don’t upgrade from 13.1 to 13.5 it won’t matter much.

> [@dfriestedt](#):
>
> Also, can I assume the web container upgrade process will make necessary changes to the data tables, etc?

Yes.

---

_[View the full topic](https://meta.discourse.org/t/does-web-based-updates-replace-rebuilding-the-container/102090)._