Updated Version (markdown)

Version.md

@@ -3,6 +3,16 @@
 In order to use a specific version of NetBox, you need to check out the respective version of NetBox Docker.
 [Carefully check the release notes](https://github.com/netbox-community/netbox-docker/releases) to learn which version of NetBox Docker works with which version of NetBox.
 
+Your most important resource when selecting a valid image is the list of tags on the docker up:
+https://hub.docker.com/r/netboxcommunity/netbox/tags
+Identify here the target netbox version you'd like, then find the netbox-docker version on the release page that suppports it.
+Do the same thing for your currently running versions.
+
+If you are coming from old versions, also check the requirements for netbox itself (i.e. the PostgreSQL version)
+https://netboxlabs.com/docs/netbox/installation/upgrading/
+
+
+
 Then proceed to checkout the respective NetBox Docker version:
 
 ```bash
@@ -43,4 +53,41 @@ docker compose pull netbox
 docker compose up -d
 ```
 
-[netbox-github]: https://github.com/netbox-community/netbox/releases
+[netbox-github]: https://github.com/netbox-community/netbox/releases
+
+
+
+Example:
+
+You're logging into netbox and get a message saying
+
+    New Release Available
+[NetBox v4.3.2](https://github.com/netbox-community/netbox/releases/tag/v4.3.2) is available. Upgrade Instructions
+
+
+You check your running versions in the lower left corner. 
+- In recent versions, both the version of netbox and netbox-docker are displayed
+- in older versions you'll only see the version of netbox
+
+
+You want to upgrade in steps - for example:
+
+- Coming from netbox-docker 3.2.0 running netbox 4.2.0
+- Targeting netbox 4.3.2 as in the upgrade notice
+- 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__
+
+(supposedly safe) Solution:
+
+
+- Run a database backup with a name that tells you the netbox version
+- change branch from netbox-docker 3.2.0 to 3.2.1 (you'll see the VERSION file increment)
+- optionally rebuild your image if you had plugins using `FROM netboxcommunity/netbox:v4.2.3-3.2.1`
+- if the newest netbox-docker minor release supports the newest netbox minor you can jump with both at the same time - 4.2.0->4.2.3, 3.2.0->3.2.1
+- start and test
+- then upgrade netbox to the last version supported in netbox-docker 3.2.1, which was 4.3.0
+- optionally rebuild your image using `FROM netboxcommunity/netbox:v4.3.0-3.2.1`
+- start and test
+- change branch to netbox-docker 3.3.3
+- optionally rebuild your image using `FROM netboxcommunity/netbox:v4.3.2-3.3.0`
+- start and test
+- Run a database backup with a name that tells you the new netbox version