I have a self-hosted installation with working plugins, but Discourse keeps updating automatically without permission, and just recently the forum broke because a plugin was no longer compatible. Since my use case is already defined and I don’t actually need the new Discourse features, how do I disable updates so the plugins don’t break?

[图片] Willy: Discourse keeps updating automatically without permission Discourse doesn’t update automatically. We don’t even have an automatic update feature. Someone may be updating your forum? Or did you add a manual background job to do it on the host server?

That’s mind-blowing because I don’t have any plugins that perform automatic updates, and I can’t see anything in the app.yml file, but you already said that Discourse doesn’t have that feature. Is there any method to retrieve the exact moment (date and time) when Discourse was last updated?

[图片] Willy: Is there any method to retrieve the exact moment (date and time) when Discourse was last updated? The date can be found at the bottom of /admin (if you’re on the old page). Should see it like: [CleanShot 2026-06-25 at 15.46.23] Maybe it’s somewhere else more detailed though… :thinking:

Okay, I see. It says the last update was 3 hours ago, and 3 hours ago I ran: ./launcher rebuild app Does that command update Discourse? So how do I install plugins without updating Discourse?

[图片] Willy: Does that command update Discourse? Yes, that’s the main way to update Discourse. [图片] Willy: So how do I install plugins without updating Discourse? You are either installing plugins or you are at [图片] Willy: my use case is already defined and I don’t actually need the new Discourse features While it’s technically possible to pin Discourse to a specific version while installing plugins, this requires a very careful analysis of version compatibility, with many plugins assuming an up to date version of Discourse.

it’s technically possible to pin Discourse to a specific version while installing plugins How do I do that? this requires a very careful analysis of version compatibility, with many plugins assuming an up to date version of Discourse The plugins are mine, I don’t want them to break, I already had a bad experience when Discourse changed the architecture or whatever. I wish the forum would follow Golang’s philosophy.

Have you considered switching to the ESR release instead of pinning a specific version? Then you would still receive the security fixes but only have to deal with other changes every 6 months. [图片] Switching between Discourse release channels / versions Self-Hosting bookmark This guide explains how to configure the release channel of your Discourse instance. person_raising_hand Required user level: System Administrator warning Console access is required. Managing your Discourse instance’s channel determines the frequency and type of updates you receive. This guide explains the channels available and provides a step-by-step approach to changing the branch on your setup. Summary Discourse offers several channels for tracking software updates: lat…

That’s a start, but I’ll still wait for someone who can explain how to stay on a specific version.

I am not sure what exactly you are waiting for. The topic I linked already explains how to configure the version you want to install. [图片]Switching between Discourse release channels / versions Follow these steps to configure the desired branch in your Discourse instance: Access the configuration file Open the app.yml configuration file by running the following commands in your console: cd /var/discourse git pull nano containers/app.yml The nano editor will open the configuration file. 2. Edit the tracking branch Locate the version parameter by searching for the word “version” in the file: params: ## Which Git revision should this container use? (default: latest) #version: latest Uncomment the version line. Replace latest with your desired branch or tag name (e.g., esr).Example: params: ## Which Git revision should this container use? (default: latest) version: esr Save and exit Press Ctrl+O to save your changes. Press Enter to confirm. Use Ctrl+X to exit the editor. Rebuild the container Once the changes are made and saved, rebuild the container to apply the new configuration: git pull ./launcher rebuild app You said you don’t want the ESR version, but a specific one. But the same process applies whether you use a branch, tag, or a specific commit hash - you simply replace the value of version accordingly. You can also find some examples of that in the forum [1] [2] :warning: I still recommend avoiding pinned commits in production, since you will not receive security updates or fixes unless you manually track them.

But those are revisions, basically, which branch I want to use. I’m saying to fix it at a version like 2026.6.0 and never update from that version. What you’re proposing keeps changing between versions, just on a different branch.

能否禁用 Discourse 更新？

产品支持安装

chapoi 2026 年6 月 25 日 13:46 5

你可以在 /admin 页面底部找到这个日期（如果你使用的是旧版界面）。

应该会看到类似这样的内容：

不过可能还有更详细的记录位置……

话题		回复	浏览量
Disabling Automatic Updates Product Support	9	918	2023 年5 月 15 日
How to avoid Discourse BETA version and keep only stable? Product Support	1	1020	2020 年7 月 28 日
"Your Discourse installation is out of date" when using release/2026.7 Self-hosting	0	70	2026 年10 月 9 日
Is it possible to upgrade Discourse up to a number of commits in the version? Development	4	2107	2019 年6 月 25 日
Completely automatic updates Feature	13	4441	2018 年6 月 27 日

能否禁用 Discourse 更新？

相关话题