Regarding update and upgrade issues after deploying Discourse

Hello everyone, I am a Discourse beginner, and I would like to ask: after successfully deploying Discourse, I see an updatable version in the admin panel. I have found two upgrade methods:

  1. Via SSH, enter the Discourse directory and run ./launcher rebuild app to upgrade and update.
  2. Via Discourse Admin - Updates - Update Discourse.

What is the difference between these two methods? Which upgrade method should be prioritized?

Thank you.

1 Like

both are good and (I think) basically do the same thing. Only caveat is that occasionally the UI upgrade will not work and a command line rebuild will be necessary. An example of this was when the database version needed to be upgraded.

So…. run a back up, use the online admin interface but be prepared to have to go into the command line if you have to.

1 Like

Once, after upgrading through the backend administrator panel, image attachments went missing, and I only managed to recover them through recover. I don’t know the reason why, so since then, I have only used rebuild for updates and upgrades.

i only update via ssh but both should work for updating Discourse. you should update Docker from command line though (updates are less often).

2 Likes

How often do you typically rebuild? Or do you wait for a few official updates before rebuilding?

Discourse

It depends on which site I am updating and when the best time is. on a busy production forum, generally I update/rebuild once a week, but I will also do it sooner if I know a specific update has a fix I want, or if I need to make a change to app.yml (installing a plugin, for example). you probably don’t have to update that often though. on my dev instance I rebuild probably at least every second day.

Docker

I update as soon as it is conveniently possible when there is an update available.

2 Likes