I went exactly the same route. Years of proxmox realizing it is not KISS in any way for my use cases. Switches to Nixos on ZFS root (so no bash installation scripts ;) ).
However, docker has not the same level of isolation and security as VMs. I am currently looking into gVisor for that.
My t440s is 10 years now. Still going strong as my main and only computer. Although, those frame.works’s look really nice.
It’s the former. In many cities cars are required to have a badge in their windshield signifying / signaling (?) how polluting (is that a word?) their car is. From red (really old and bad) to green. This applies to both gasoline and diesel cars and e.g. really dirty diesel cars (euro 1 and 2 norm) are completely forbidden (red badge).
Then additionally some cities have streets banning diesel cars completly or requiring some very strict exhaust norm (euro 6? Euro 7; I don’t know).
How is this enforced. E.g. by checking parking cars for their badge or by selectively stopping cars (and be it for other violations, yes). There obviously are some fines. That’s it I think and it mostly works (I guess, not living in a city myself).
Ansible and Terraform united. Make something out of it IBM.
You just update DNS entry if your ip changes (automatically over api ofc)
Have a look at kopia. But a proper backup is never set and forget.
You’re joking. You’re joking, right? Right?
Just self host the bridges. I mean if you trust your phone more than your server, this won’t help.
Wuhu that’s nice, thank you! But it is speech-to-text, right?
Never worry about backups or lost data etc, as the provider would take care of it
This is not how it works. You still have to backup your data!
Your account can be closed due to various reasons, you accidentally delete files, some malware deletes files without you noticing it before it is too late.
A friend of mine lost some important data because of the ovh server container fire incident. Ovh had no backups.
Have been a fan of a what I called “simplified” git flow until recently when I realized I am basically doing trunk based branching with two trunks (Main and dev). The static dev branch had its appeal for static deployments (no test deploy from varying feature branch, but still not main); however, for gitops and for general simplicity forcing yourself and the team to main has its advantages. E.g knowing that every deployment is from main.
Having had massive problems using normal swap in combination with zfs in out of memory situations with high memory pressure I now only - but as default - use zram on bare-metal machines.
But if not (for disaster recovery only) it is pretty cheap. Like 1$/TB/month.
Debian. On every computer with a physical keyboard. And all servers. Mainly because of philosophy, stability, release cycle (2 years for major updates which I find neither too longnkor too short) and having gotten (is that proper english lol) used to it.
Just if somebody else needs this for ZFS: https://blog.juhefa.de/posts/zfs-replace-disk/