summary refs log tree commit diff
path: root/develop/print.html
diff options
context:
space:
mode:
authoranoadragon453 <anoadragon453@users.noreply.github.com>2024-02-22 17:38:07 +0000
committeranoadragon453 <anoadragon453@users.noreply.github.com>2024-02-22 17:38:07 +0000
commite7a7f90a48e0070d2a3a37eb79ac13636f3b2e12 (patch)
tree56a25034b64db8b07e0853471e80702716c75590 /develop/print.html
parentdeploy: 7c1c011942ebeb7ab781ccb3640922290159a98c (diff)
downloadsynapse-e7a7f90a48e0070d2a3a37eb79ac13636f3b2e12.tar.xz
deploy: 8de3283ebe520e945ccfb66242f4795ecdd0d1f4
Diffstat (limited to 'develop/print.html')
-rw-r--r--develop/print.html19
1 files changed, 19 insertions, 0 deletions
diff --git a/develop/print.html b/develop/print.html
index f308b728b5..915706cd46 100644
--- a/develop/print.html
+++ b/develop/print.html
@@ -1843,6 +1843,22 @@ v1.61.0.</p>
 <tr><td>v1.92.0 – v1.97.0</td><td>v1.90.0</td></tr>
 <tr><td>v1.98.0 – v1.101.0</td><td>v1.96.0</td></tr>
 </tbody></table>
+<h2 id="upgrading-from-a-very-old-version"><a class="header" href="#upgrading-from-a-very-old-version">Upgrading from a very old version</a></h2>
+<p>You need to read all of the upgrade notes for each version between your current
+version and the latest so that you can update your dependencies, environment,
+config files, etc. if necessary. But you do not need to perform an
+upgrade to each individual version that was missed.</p>
+<p>We do not have a list of which versions must be installed. Instead, we recommend
+that you upgrade through each incompatible database schema version, which would
+give you the ability to roll back the maximum number of versions should anything
+go wrong. See <a href="upgrade.html#rolling-back-to-older-versions">Rolling back to older versions</a>
+above.</p>
+<p>Additionally, new versions of Synapse will occasionally run database migrations
+and background updates to update the database. Synapse will not start until
+database migrations are complete. You should wait until background updates from
+each upgrade are complete before moving on to the next upgrade, to avoid
+stacking them up. You can monitor the currently running background updates with
+<a href="usage/administration/admin_api/background_updates.html#status">the Admin API</a>.</p>
 <h1 id="upgrading-to-v11000"><a class="header" href="#upgrading-to-v11000">Upgrading to v1.100.0</a></h1>
 <h2 id="minimum-supported-rust-version"><a class="header" href="#minimum-supported-rust-version">Minimum supported Rust version</a></h2>
 <p>The minimum supported Rust version has been increased from v1.61.0 to v1.65.0.
@@ -16344,6 +16360,9 @@ for file in $source_directory/*; do
     fi
 done
 </code></pre>
+<h2 id="how-do-i-upgrade-from-a-very-old-version-of-synapse-to-the-latest"><a class="header" href="#how-do-i-upgrade-from-a-very-old-version-of-synapse-to-the-latest">How do I upgrade from a very old version of Synapse to the latest?</a></h2>
+<p>See <a href="usage/administration/../../upgrade.html#upgrading-from-a-very-old-version">this</a> section in the
+upgrade docs.</p>
 <h2 id="manually-resetting-passwords"><a class="header" href="#manually-resetting-passwords">Manually resetting passwords</a></h2>
 <p>Users can reset their password through their client. Alternatively, a server admin
 can reset a user's password using the <a href="usage/administration/../../admin_api/user_admin_api.html#reset-password">admin API</a>.</p>