Does web based updates replace rebuilding the container?

Installazione
1

I have been doing web based upgrades at admin/upgrade and since I tend to have very high up times, does this replace replace the updates that are done when rebuilding the container with ./launcher rebuild?

Also, when I reboot does the container auto-update itself?

Thanks!

2

Majority of your updates can be done via the web, once in a few months you need to rebuild to get updates to the base image. If we deem it critical we will force it upon you.

4 Mi Piace
3

I was just upgrading stuff, and what a timing! I got a error

Discourse requires Ruby 2.5.2 or up
Docker Manager: FAILED TO UPGRADE
#<RuntimeError: RuntimeError>

So I guess I’ll stick to rebuilding every week or so. The downtime is bad, but I don’t need to be up 99,9% of the time.

1 Mi Piace
4

Oh … we got to force a rebuild here I just fixed that so others do not see this issue.

5 Mi Piace
5

I don’t know if I’m doing something wrong, but I tried to do a rebuild via terminal and I’m getting this:

error: Your local changes to the following files would be overwritten by merge:
        templates/import/mbox.template.yml
        templates/web.ssl.template.yml

But I don’t use those templates, and I do not interact with templates files. I delete them and can proceed, but any idea why this could be happening?

And I’m not sure if you were being sarcastic, I have no reason to lie or anything…

6 
cd /var/discourse
git reset --hard
git pull
./launcher rebuild app
3 Mi Piace
7

Ok I’m trying to automate this, with a cronjob to rebuild the container after every reboot.

@reboot sleep 300 && /opt/discourse/launcher rebuild app > /root/discord-update.log

It seems to be working, but for some reason the log file get cut after Removing old container.

Is there some kind of recommended way to get automatic updates working?

I had to wait 300 seconds for the docker daemon to start. With this settings it should take 10 min after reboot to be back on air. Rebuilding takes 5 min with a SSD and 2 vCPU.

8

If you’re concerned about uptime, you should switch to a two container install.

3 Mi Piace
9

For some reason the output of my script stops redirecting to the file… is there a guide on this two container install?

5 min of downtime every month is still like 99,5% uptime so unless the two container install is easy to do/manage it doesn’t worth it…

10

For a description see: How to move from standalone container to separate web and data containers.

For a normal rebuild/upgrade It’s pretty much the same as a single container install. Rather than

./launcher rebuild app

you do

./launcher bootstrap web_only && ./launcher destroy web_only && ./launcher start web_only
5 Mi Piace
12

I’m getting ready to migrate to separate data containers as described above.

When upgrading, do I ever need to update the data container? If so, when?

Also, can I assume the web container upgrade process will make necessary changes to the data tables, etc?

14

Quando c’è una modifica a postgres o redis. Sapere quando ciò è accaduto è una questione di tenere traccia delle cose ed è il motivo per cui molte persone pensano che la configurazione a due container sia troppo difficile. Ho script che controllano le versioni di postgres e redis e aggiornano il container dei dati se è stata apportata una modifica. Tali modifiche avvengono ogni anno o due, anche se gli aggiornamenti sub-base avvengono un po’ più spesso. Generalmente, se non si aggiorna da 13.1 a 13.5, non farà molta differenza.

Sì.

1 Mi Piace
15

Questo argomento è stato chiuso automaticamente dopo 15 giorni. Non sono più consentite nuove risposte.