ulysses4ever encountered issues upgrading their Discourse instance because /var/discourse only contained a shared directory and was not a Git repo. The instance was running an outdated version (2.1.0, from mid-2018), prompting urgent advice to upgrade for security and feature reasons jomaxro. Initial suggestions included migrating to a new VM or server and restoring from backup pfaffman, Stephen, though ulysses4ever clarified they were on dedicated hardware with no spare machine. The official Docker-based install guide was referenced pfaffman. Eventually, the original admin helped locate the actual Git repo in /var/docker, allowing a successful standard upgrade to version 2.6 ulysses4ever. pfaffman noted /var/docker was once the standard location. Suggestions to document the path riking or symlink /var/discourse to /var/docker were offered, though the latter was cautioned against due to potential conflicts michaeld.
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 shared directory in there, and git pull fails accordingly (it’s not a git repository). What should I do?
This is indeed most likely what’s going on. It’s running Discourse 2.1.0 (if it makes things clearer).
That’s the thing: my instance IS on dedicated hardware.
So, I understand currently no Docker involved. At least, not manually. At least, it’s good to know that there is just one way to set it up and it uses just git clone and the setup script.
What bothers me is how I would gently scrap the old version, given that everything is happening on an actual physical machine (i.e. nothing “virtual”). I did the backup, that’s easy. Now what?
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.
Thank you for the feedback, but that’s not being questioned: I am trying to update. I wasn’t the admin of this instance before yesterday and I know the importance of updates.
Thanks all for the answers! I asked the old guy, and he helped. The Git repo was inside /var/docker instead of /var/discourse for some reason. From there, it was possible to apply the standard procedure. We are now at the latest release (2.6), yay!