Is there any faster way to re-build the site?

[45thj5ej]

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.

[pfaffman (Jay Pfaffman)]

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.

[45thj5ej]

Hi, this post from 2016? Faster rebuilds?

Is it not outdated?

[Ed_S]

Perhaps see

Move from standalone container to separate web and data containers

This is an advanced setup. Don’t follow this unless you are experienced with Linux server administration and Docker. 2 Container Setup for a New Site Added by @pfaffman 2019-12-11. NOTE: If you want to create a 2 container site you can do this: ./discourse-setup --two-container It works just like normal except it’ll create separate data and web_only containers and generate a random password for the database. If you already have an app.yml you’ll need to rename it, or discourse…

[pfaffman (Jay Pfaffman)]

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