Description
Secrets used to be managed with a secrets.json file in this repo, unencrypted on disk but encrypted with git-crypt when pushed to a remote. They're now in a private repo, mostly managed using sops, although some have to stay in secrets.json in cleartext. Git-crypt is no longer used since it must be in cleartext on the remote in order to pull it in as a flake input.
Steps takenEmergentMind's repo does something like this, but I haven't been able to get it working so far.
Description Secrets used to be managed with a secrets.json file in this repo, unencrypted on disk but encrypted with git-crypt when pushed to a remote. They're now in a private repo, mostly managed using sops, although some have to stay in secrets.json in cleartext. Git-crypt is no longer used since it must be in cleartext on the remote in order to pull it in as a flake input.
Steps taken EmergentMind's repo does something like this, but I haven't been able to get it working so far.