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…

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…

[image] 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 y…

[image] 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…

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.

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

[image] 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 problema…

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:

Major upgrade -- best practices?

Support Self-hosting

Ethsim2 (Ethan ) August 27, 2025, 3:47pm 2

deploy a test forum. I have never forked anything

Topic		Replies	Views
Upgrading Old Discourse Installation Support	2	440	July 24, 2021
Upgrading from 2.6.0.beta1 to latest stable Support server-resources , backups	7	230	September 22, 2025
How to upgrade Discourse from 1.6.1 version to latest_release Support	13	1708	May 19, 2023
What to be aware of when updating an old Discourse version to the latest? Self-hosting	5	396	June 22, 2024
My install is 16,359 commits behind! Advice? Self-hosting	15	318	April 17, 2025

Major upgrade -- best practices?

Related topics