Dear all, I have a Discourse instance setup by the previous admin on our department web server. I don’t know much about Discourse, but it requires updating and suggests doing cd /var/discourse git pull ./launcher rebuild app But when I cd into /var/discourse I see only the…

[afbeelding] ulysses4ever: . The Git repo was inside /var/docker instead of /var/discourse for some reason Aha! That was the recommended place in a time long, long ago (before I started using Discourse 4 years ago). Looks like my “ask the old guy” solution really worked!

You should do a clean install on a new VM, make a backup, and restore it to the new installation. If you don’t like that answer, then you should get whoever set that thing up to come and fix it.

@pfaffman What do you mean by a new VM? A Docker image for Discourse? The issue is I can’t find a manual how to manage Discourse through Docker.

A new VM means a new virtual server, assuming your instance isn’t on dedicated hardware. If you have Discourse running but /var/discourse is empty it’s either a very very old installation or an unsupported package. Either way, you should create a backup, spin up a new virtual server, follow the st…

[afbeelding] ulysses4ever: The issue is I can’t find a manual how to manage Discourse through Docker. You do this: https://meta.discourse.org/t/discourse-official-standard-installation/142537

[afbeelding] Stephen: it’s either a very very old installation This is indeed most likely what’s going on. It’s running Discourse 2.1.0 (if it makes things clearer). [afbeelding] Stephen: A new VM means a new virtual server, assuming your instance isn’t on dedicated hardware. That’s t…

Now install on a different machine. A VM is preferable as it’s easier to scale up resources. System requirements are in the install doc. Once you have the new install running restore that backup. What kind of instance is this? How busy is it? Is it in constant use?

[afbeelding] ulysses4ever: It’s running Discourse 2.1.0 Oh my…that’s from late mid 2018. You definitely want to update. Besides missing numerous great features, there have been quite a few, including some critical, security fixes that you do not have.

[afbeelding] Stephen: Now install on a different machine. Unfortunately, I don’t have a different machine. [afbeelding] jomaxro: Oh my…that’s from late mid 2018. You definitely want to update. Thank you for the feedback, but that’s not being questioned: I am trying to update. I wasn’t…

I recommend leaving some documentation just in case: echo "it's in /var/docker" > where-is-launcher

That’s a good idea. Or maybe cd /var/ ln -s /var/docker discourse Though that might confuse launcher.

How to upgrade if `/var/discourse` has only `shared` and is not git repo

Ondersteuning

pfaffman (Jay Pfaffman) 17 juli 2020 om 00:12 5

You do this: https://meta.discourse.org/t/discourse-official-standard-installation/142537

Topic		Antwoorden	Weergaven
Upgrading installation from 2016 Support	3	498	28 mei 2020
Simplified Discourse install? Self-hosting	2	1367	29 april 2019
Upgrade container - keeping config and data Self-hosting	8	2399	15 juni 2022
Updating Discourse from v1.0.1 Support	13	1172	6 juni 2017
Manually update Discourse and Docker image to latest Self-Hosting how-to	13	109740	16 januari 2025

How to upgrade if `/var/discourse` has only `shared` and is not git repo

Gerelateerde topics