From 95c7a394dc7d75a1bced03dc65e5a9d9f40e84be Mon Sep 17 00:00:00 2001 From: Nick Sweeting Date: Tue, 22 Mar 2022 20:31:34 -0400 Subject: [PATCH] Updated Upgrading or Merging Archives (markdown) --- Upgrading-or-Merging-Archives.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Upgrading-or-Merging-Archives.md b/Upgrading-or-Merging-Archives.md index f5118d8..a82c01a 100644 --- a/Upgrading-or-Merging-Archives.md +++ b/Upgrading-or-Merging-Archives.md @@ -3,12 +3,12 @@ *Note: It's recommended to only upgrade one major version at a time. e.g. if you're on `v0.4.14`, upgrade to `v0.4.2`, then to `v0.5.6` (the latest available minor version for each major version), then from there to `v0.6.3`, not straight from `v0.4.14` -> `v0.6.3`. You can specify exact versions with pip like so: `pip install archivebox==0.6.3` or with docker `docker pull archivebox/archivebox:0.6.3`. Upgrading directly across multiple major versions may work in some cases, but is not recommended for maximum data safety.* -The list of all ArchiveBox releases/versions can be found here: https://github.com/ArchiveBox/ArchiveBox/releases +**✅ Upgrading checklist:** 1. Find the version you want to upgrade to on https://github.com/ArchiveBox/ArchiveBox/releases 2. **Read the release notes carefully** for any instructions or extra steps around upgrading 3. **Make a full backup** of your `index.sqlite3` and `archive/` content before upgrading! -4. Follow the steps below depending on your setup +4. Follow the steps below depending on your setup (repeating as necessary for each major version if upgrading across multiple major versions) ArchiveBox uses the Django migrations system for deterministic, atomic, safe upgrades, so your DB should always be left in a consistent state in the event of a failure or power outage.