My Discourse installation has fallen out of date (3.2.0.beta4-dev) and I need to upgrade to 3.5. I am worried about disturbing things and use a few plugins/integrations that I haven’t wanted to change ( WP Discourse , login through Wordpress with membership info and Category Lockdown plugin) and I hav…

deploy a test forum. I have never forked anything

If you want to be safest, you’ll spin up a new server, Move a Discourse site to another VPS with rsync (I’d skip the database files), and restore a backup. I’m pretty sure that you’ll need to PostgreSQL 15 update . There should be no issues with WP Discourse . You can check Discourse Category Lockdo…

[图片] pfaffman: spin up a new server, Move a Discourse site to another VPS with rsync (I’d skip the database files), and restore a backup This has some good side-effects, of ensuring you have a recent backup and you have a safe copy of that backup. You do need to do those things, however you …

[图片] Ed_S: This has some good side-effects, of ensuring you have a recent backup and you have a safe copy of that backup. You do need to do those things, however you approach your upgrade. Yeah. Actually, knowing that you can spin up a new server and restore a backup. I had to do this once re…

Best practice? Keep a checklist somewhere, you can add one in the UI>admin>update by adding this CSS to your theme(../admin/customize/themes/ edit>css) if someday you or someone would have the idea to update too quickly : .admin-contents.update .d-nav-submenu::before {content:“Update checklist” : B…

Checklists are a good idea. For myself, contemplating an upgrade, I wait for a release, wait a couple of days, wait for a weekday, read the Bugs and Support categories to see what problems people are having. And wait for those problems, if any, to be fixed.

[图片] Ed_S: I wait for a release You are on stable presumably? Otherwise this strategy wouldn’t help with continuous integration …

[图片] merefield: You are on stable presumably? No, I’m on tests-passed. It’s true that my delay of a few days will allow some stray further commits to be added to the repo, but at the same time it allows some mistakes to have been corrected. Almost all commits, of course, are not problematic…

There is a flurry of upgrades just after a new beta, so even on tests-passed, a few days after an upgrade is a good time for an upgrade. Or, perhaps we share the same flawed logic!

I remain unconvinced without a supporting graph. :innocent:

重大升级 -- 最佳实践/

支持安装

pfaffman (Jay Pfaffman) 2025 年8 月 29 日 16:19 12

我认为你会看到，嗯，例如，在发布后的五天内，与其余时间相比，与错误相关的提交百分比（不确定如何量化——也许只是计算那些提交信息中有“FIX”的？）

话题		回复	浏览量
Upgrading Old Discourse Installation Support	2	443	2021 年7 月 24 日
Upgrading from 2.6.0.beta1 to latest stable Support backups , server-resources	6	265	2025 年8 月 30 日
How to upgrade Discourse from 1.6.1 version to latest_release Support	11	1762	2019 年9 月 27 日
What to be aware of when updating an old Discourse version to the latest? Self-hosting	5	414	2024 年6 月 22 日
My install is 16,359 commits behind! Advice? Self-hosting	14	377	2025 年3 月 18 日

重大升级 -- 最佳实践/

相关话题