# Is er een snellere manier om de site opnieuw op te bouwen?

**URL:** https://meta.discourse.org/t/is-there-any-faster-way-to-re-build-the-site/301411
**Category:** Self-hosting
**Created:** [28 maart 2024 om 20:37 UTC](https://meta.discourse.org/t/is-there-any-faster-way-to-re-build-the-site/301411 "2024-03-28T20:37:15Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![45thj5ej](https://avatars.discourse-cdn.com/v4/letter/4/34f0e0/32.png) [@45thj5ej](https://meta.discourse.org/u/45thj5ej)
#### Post date: [28 maart 2024 om 20:37 UTC](https://meta.discourse.org/t/is-there-any-faster-way-to-re-build-the-site/301411/1 "2024-03-28T20:37:15Z")

</div>

I host it on a VPS. Anytime I rebuild the site (adding plugin, etc) it takes like 15mins total of downtime, which sure, in the grand scheme of life, 15mins is nothing, but in the tech world where downtime is key not to ever have, it’s crucial.

---

<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: [28 maart 2024 om 21:28 UTC](https://meta.discourse.org/t/is-there-any-faster-way-to-re-build-the-site/301411/2 "2024-03-28T21:28:23Z")

</div>

The easiest solution is a two container setup which has a separate data container. You can build the new one while the old one continues to run. The down time is then just a minute or so while the new one cranks up.

The easiest way to do that is spin up another vm and pass the --two-container switch to discourse-setup. There is a topic about how to do it by hand.

---

<div class="post-metadata">

### Author: ![45thj5ej](https://avatars.discourse-cdn.com/v4/letter/4/34f0e0/32.png) [@45thj5ej](https://meta.discourse.org/u/45thj5ej)
#### Post date: [30 maart 2024 om 03:41 UTC](https://meta.discourse.org/t/is-there-any-faster-way-to-re-build-the-site/301411/3 "2024-03-30T03:41:14Z")

</div>

Hi, this post from 2016? [Faster rebuilds?](https://meta.discourse.org/t/faster-rebuilds/40341)

Is it not outdated?

---

<div class="post-metadata">

### Author: ![Ed\_S](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ed_s/32/134015_2.png) [@Ed\_S](https://meta.discourse.org/u/Ed_S)
#### Post date: [30 maart 2024 om 08:39 UTC](https://meta.discourse.org/t/is-there-any-faster-way-to-re-build-the-site/301411/4 "2024-03-30T08:39:51Z")

</div>

Perhaps see

> [@Move from standalone container to separate web and data containers](https://meta.discourse.org/t/move-from-standalone-container-to-separate-web-and-data-containers/29413):
>
> warning This is an advanced setup. Don’t follow this unless you are experienced with Linux server administration and Docker. You also need to pay close attention to commits to discourse\_docker to make sure you notice if there’s a version bump for postgres or redis. Converting your Current Setup I managed to migrate to two containers. If anyone else needs instructions, this is how it worked for me. The process includes backup, setting up separate web and data containers and restore data. …

---

<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: [30 maart 2024 om 10:14 UTC](https://meta.discourse.org/t/is-there-any-faster-way-to-re-build-the-site/301411/5 "2024-03-30T10:14:56Z")

</div>

This is what I was referring to. It will never be outdated until or unless the basic installation script changes.
