Muehe

Well no actually, at least according to the guy himself (added note and emphasis):

Now I do not always do things just as the others want them done. I consider what the others probably believe, and then do the opposite on principle. So if Mr. Stalin expected that we would attack in the center [Moscow], I did not want to attack in the center, not only because Mr. Stalin probably believed I would, but because I didn’t care about it any more at all. But I wanted to come to the Volga, to a definite place, to a definite city. It accidentally bears the name of Stalin himself, but do not think that I went after it on that account.

Indeed, it could have an altogether different name. But only because it is an important point, that is, there 30 million tons of traffic can be cut off, including about 9 million of oil shipments. There all the wheat pours in from those enormous territories of the Ukraine, of the Kuban territory, then to be transported to the North. There the manganese ore was forwarded. A gigantic terminal was there; I wanted to take it.

Now you can of course question if the narrative given in a propaganda speech is accurate, but I have never really seen sources for Hitler wanting to attack because of the name. So it kind of seems like a persistent urban legend to me.

Oh I see. You mean like v3.0.1 will be stable, and v3.1.0 will be stable. Yeah that’s true. But v3 (as in v3.0.0) is breaking. At least that’s how I have always seen the terms used.

No, v3 is a release with breaking changes:

This release includes several breaking changes; read the full migration guide here. It’s worth mentioning that many of the breaking changes are updates to API endpoints and only affect third-party tools that integrate with Immich’s API. For the vast majority of users, updating works exactly as it always has.

immich.app/blog/v3.0.0-release

That’s why the major version was increased, it implies breaking changes in semantic versioning, which Immich is doing since v2 apparently:

Given a version number MAJOR.MINOR.PATCH, increment the:

1. MAJOR version when you make incompatible API changes
2. MINOR version when you add functionality in a backward compatible manner
3. PATCH version when you make backward compatible bug fixes

semver.org

Well if you want the real basics of self-hosting then depending on your level of knowledge you may want to follow a Linux tutorial like this one: labex.io/linuxjourney

This will teach a lot of basic knowledge and terminology you may need when setting up or maintaining containers and VMs. Admittedly, this is somewhat tangential knowledge to your immediate goals, but if you want to actually use your self-hosted stuff remotely later this will become critical to doing so safely.

As for the map, for me it was something like:

Local LXC/QEMU → Remote LXD over SSH on a RPi → Proxmox on a dedicated box through the webinterface

In hindsight I would have started with Proxmox directly though I guess. One big downside is it doesn’t integrate well with Docker containers, you have to set up a full VM as your Docker host. On the upside though you can install LXC containers from www.turnkeylinux.org in a few clicks, so it’s very good for just testing stuff out and playing around.