The Incredible Laser

https://troet.cafe/@IncredibleLaser

Public Key

npub1nfm3cr8g9c0ynmdktcvd5kz2llfs43sulsdmqt9ap6sy9vrc949s4hp6t6

NIP-05 Address

[email protected]

Profile Code

nprofile1qqsf5acupn5zu8jfakm9uxx6tp90l5c2ccw0cxas9j7sagzzkpuz6jcprpmhxue69uhhyetvv9ujumt0d4hhxarj9ecxjmntacjj60

Publishing to

relay.momostr.pink

Author Public Key

npub1nfm3cr8g9c0ynmdktcvd5kz2llfs43sulsdmqt9ap6sy9vrc949s4hp6t6

Show more details

Last Notes

2025-12-16 07:55:07 GMT

- reply

I recently migrated to the dendritic organization approach which in my opinion is best described at https://not-a-number.io/2025/refactoring-my-infrastructure-as-code-configurations
(example implementation at https://github.com/mightyiam/infra)
From that, I deploy my machines with deploy-rs. Should note that I also have a json file from where I import host properties like address, ssh user etc
Also modules and packages live in a seperate repository and not along my machines

2025-12-14 21:42:09 GMT

- reply

good luck on the journey. I think I had a similar approach when I started though technically, the first two or three machines I migrated did not share a common flake.
I'm pretty sure you'll migrate off that layout / setup at one point for maintainability reasons, but you still have some months until that bothers you ;)

2025-11-21 17:44:49 GMT

- reply

I've always just used either the plain iso for my servers or the nixos-anywhere kexec image in case the machine is remote only. The iso contents don't really matter in my opinion if you can just push the config.
Different story for something I did for work where I included specific tools to help with the setup process. But for single machines, default does the trick.
There's nothing wrong with tinkering though, just my personal opinion.