On NixOS we get one new grub menu entry per “deployment”, be it when you deploy to another host or the local one. They both then get a new grub entry. Of course you can still shoot yourself in the foot by making your system inaccessible remotely, by screwing up ssh config for example. There’s also a solution for that called deploy-rs which has a magic rollback feature which rolls back the system if it can’t connect back to the computer initiating the deployment https://github.com/serokell/deploy-rs?tab=readme-ov-file#mag...
I’m using these features since multiple years now and can vouch for them.
Not exactly related to your initial question but I also have my system build in CI and do some playwright tests which become more and more comprehensive as time passes. This all gives me quite a lot of confidence I’ll find an issue early or be able to revert back.
I’m deploying on my server and it self hosts 10 or so services. Like Nextcloud and Vaultwarden. The playwright tests are to test those. It’s pretty basic like just checking I can create a user and still login. But it still caught a few regressions. And they’re still WIP. I’m getting close to being able to validate the LLDAP + Authelia config works too. It’s particularly useful in conjunction with automatically running flake update in CI. So all inputs get updated on a schedule and the tests give some level of guarantee that my server won’t break. It’s essentially QA tests automated.
That’s so true. I can see it too. The technology to make that must be super fun to work on but please I hope this will never happen. Can you imagine turning the whole sky as a giant pixelated screen to constantly show us ads? That’s as dystopian as it gets. Add to that the probable less than secure software to run it and hackers trying to show stuff up there. That’s something out of a Douglas Adams book. xD
Do not underestimate the joy of using something beautiful and something one crafted. Those little bit of joy add up in the end.
At least, they matter to me. I “smartened” an energy meter with an ESP32 and a photoresistor that measures every blink from the energy meter. It’s really crude but it works and everytime I go in the garage, I see the little device blink and it brings me joy. It brings me determination to pursue the next project and motivates me to no end. I know I can build stuff and that I can succeed. I know I can progress in life.
It will probably sound stupid but that’s how I interpret the author’s project.
There are still lots of people playing DnD so not all hope is lost. Or just do 6 kids and play with them, true it’s a long term investment just for one game :D
Seriously though the instructions say you can play over internet too.
Self-hosting is such a nice touch. For me it’s a requirement indeed. Thanks for making this possible!
On a different topic, may I ask how did you find your first users? This always fascinates me and TBH it’s not an uninterested question as I plan to start a business myself related to self-hosting.
With rsync, you’re replicating only the last state.
With borg, you can see all backups being made and rollback to any previous snapshot. This is true of a lot of backup solutions btw.
Concretely, if you inadvertently delete a file and this get rsynced, you cannot use the backup to restore that file. With borg you can.
I’m using these features since multiple years now and can vouch for them.
Not exactly related to your initial question but I also have my system build in CI and do some playwright tests which become more and more comprehensive as time passes. This all gives me quite a lot of confidence I’ll find an issue early or be able to revert back.
reply