My experience on other distros was that upgrading in place a system that deviated too much from “stock” would wreck the install. I would personally play it safe and backup my home folder and do a fresh install.
Just don’t forget to test your backup before formatting your drive!
Terraform is part of a movement called “Infrastructure as Code” (IaC) which allows engineers to define their cloud infrastructure using code.
This is extremely useful as it allows you to:
version infrastructure changes
automate resource and configuration creation and management
have reproducible environments (think production and staging envs, or deploying a new production env to another datacenter)
Terraform (and OpenTofu) is different to most IaC project as it is agnostic of cloud providers: you can use it to deploy infrastructure to multiple providers, where their competitors are limited to their own platform (I think of AWS’s Cloud Development Kit)
Kinoite is much more than that: it is an atomic and immutable spin of Fedora KDE. This has big implications but the gist of it is that:
You can roll back to any previous version if anything breaks
The base system cannot be modified
If you need to install RPM packages, you do that by adding “layers” on top of the base system, and these can be removed if needed to go back to a clean base system
You can switch from one spin to another by “rebasing”, but it is recommended that you remove any additional layer first and that you stick to the same desktop environment