I also share this brand of illness.

As I was reluctant going all in, having kept them in git since 2012, I still keep a few of them in their own separate repository. I load them as a nix flake input, and put the files in the expected place using nixos. Works OK, but adds a bit of a roundtrip if you are experimenting with changes often.

This also allows me to share some of them to my work machine, which uses nix, and other files on other systems that dont.

That said, I consider myself all in nix quite some time ago, and have moved more and more of the config over to the nix repo using the nix language for config instead of the input flake config file approach. Iterating on it is much faster this way.

I’ve done similar things for mismatched python dependencies in a broken Airflow setup on GCP, and got amazingly good results pointing me in the right direction to resolve the conflicting package versions. Just dumped a mile long stack trace and the full requirements.txt on it. Often worth a shot, tbh

I’ll remember that.