这里应该有一个错误，我尝试通过标签拉取v3.6.0.beta2，结果遇到下面的错误： FAILED -------------------- Pups::ExecError: cd /var/www/discourse && sudo -H -E -u discourse bash -c ' set -o errexit git fetch --tags --prune-tags --prune --force origin if [[ $(git symbolic-ref --short HEAD) == v3.6.0.beta2 ]] ; then git pul…

我继续更新这个修改造成的其他影响：安装特定分支实现了，但是想从这个分支验证升级失败了。因为在更新页面，检测不到最新的更新，导致无法在页面上操作更新。 [image] [image]

继续之前的话题，现在发现了新的问题。当本地代码库比较旧时，将导致前端编译失败或者其他错误。所以，在开始所有修改之前，必须把本地代码库更新为最新版本。 # 如果之前修改了本地代码库的，请先暂存一下 # git stash # 更新到最新 git pull # 重新应用暂存的代码，或者重新编辑对应的配置文件 # git stash pop 当本地库更新为最新版之后，才能安装之前的步骤顺利完成指定分支的构建。这里指的本地代码库是：https://github.com/discourse/discourse_docker.git 即标准安装后的代码库。

最后来一个总结。我们的需求是：安装指定版本更新本地代码库https://github.com/discourse/discourse_docker.git # 进入项目根目录 cd /var/discourse # 更新到最新版 git pull 修改要指定的版本修改 templates/web.template.yml params: version: release/2026.1 重新构建 ./launcher rebuild app 这样修改后，后面要更新升级的步骤是先更新本地代码库，但是因为我们修改了本地代码，可能会修改失败，所以大概率需要暂存本地代…

[image] singi2016cn: params: version: release/2026.1 I think it would be very unusual to configure a specific version, rather than a flavour/stream/tag, like latest or stable. I’m actually no longer sure what tags are normal and available and useful with this system.

Have you taken a look at Configure a supported tracking branch to get Discourse software updates ? Maybe it helps for understanding which tags are useful

是的，普通用户使用默认的latest就足够了。但是对应我这种场景来说，不得不研究如何使用特定版本。我总不能对boss说：“哦，很遗憾，Discourse暂时不支持检出特定版本，我们只能更新到最新版。”

这个帖子非常有用，我将仔细看一下。感谢。

[image] Moin: Have you taken a look at Configure a supported tracking branch to get Discourse software updates ? I hadn’t seen that - thanks. Looks like we should be using latest/release/esr now. I see my own (old) app.yml picks up the default by being commented out: ## Which Git revisio…

version 目前不支持标签，如果要支持，需要修改构建的脚本。本来最佳实践是： params: version: esr 但是目前，不得不修改成 params: version: release/2026.1

Interesting. Even before the new versioning strategy, beta had been a tag instead of a branch for quite a while: Upcoming changes to the beta branch of Discourse

Help deploying older versions of Discourse

Support Self-hosting

Ed_S (Ed S) March 28, 2026, 8:07pm 21

I believe version should be indented because it’s part of params.

1 Like

Topic		Replies	Views
How can i rebuild discourse without changing version? Self-hosting	11	2647	February 5, 2021
Is it possible to upgrade Discourse up to a number of commits in the version? Dev	4	1967	June 25, 2019
Docker deploy specific version of Discourse Self-hosting docker	2	451	February 5, 2024
Trouble upgrading from 3.3.0.beta1 to 3.3.0.beta6 Self-hosting	22	265	August 8, 2024
Shallow git fetch regression in discourse_docker Support	16	2345	February 5, 2021

Help deploying older versions of Discourse

Related topics