19 has federation bugs. Mainly outgoing but I’ve also seen incoming federation gradually fail. Restart the docker container routinely (cron job) until fixes come out.
Not sure I follow what the issue is, it sounds like permissions are working as expected. If you want your normal user account to have permissions you can create a group with ID of 1000 in the host OS, add your user to that group, and set permission to 770.
“usually” is very generous. Automated testing takes effort to develop and maintain, a lot more than the rest of the CICD pipeline combined. And it’s only one piece of a complete qa strategy, if it’s all you have you’re still using users as testers.
I’m more a fan of cutting up magazines myself. It’s not often you get an excuse for some crafts when you’re busy kidnapping heirs and taunting detectives.
It’d work for everything, data lives in your storage devices, not the motherboard.
Barring UEFI/bios config issues or hardware incompatibility you just swap hardware and boot up exact same as before.
You might then need to make small tweaks if things aren’t setup quite ideally. For instance if you have lemmy binding to a specific IP rather than 0.0.0.0 and you use dhcp reservations then you might need to adjust that IP in config. Or if you don’t have fstab using uuid then your mounts might be messed up. But that stuff can all be avoided and they’re minor to fix.