From 5d0998cbe939f01876740ee1a0b31a77f029db73 Mon Sep 17 00:00:00 2001 From: Florian Heigl Date: Mon, 23 Jun 2025 04:52:52 +0200 Subject: [PATCH] Updated Version (markdown) --- Version.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Version.md b/Version.md index ce956af..1d9f44e 100644 --- a/Version.md +++ b/Version.md @@ -85,6 +85,8 @@ You want to upgrade in steps - for example: - You'll look at the the releases and docker hub tags, you see that __netbox 4.3.2__ is in the latest release along with __netbox-docker 3.3.0__ - You look at the netbox requirements and see that your postgresql version (17) is fine as they only require a recent one (14) +why? You don't always need to proceed as carefully, but there might be very breaking changes; additionally plugins have different compatibility constraints and this gives you a good chance not ending up in hard to solve situations. a typical 'edge case' would be if a plugin breaks your startup also breaks, meaning some database conversions may fail, meaning you will not successfully get to the next version because your database schema will not fit the expected state. basically you can play it safe or you can learn a lot about netbox, the netbox database schema, database migration scripts and loading backups during startup, all in a very short time frame. + ### (supposedly safe) Solution: @@ -102,3 +104,4 @@ You want to upgrade in steps - for example: - Run a database backup with a name that tells you the new netbox version In the UI the version string might need a full reload of the page to update. +