refactor: used a sops template for the mollysocket vapid key #22
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "mollysocket-vapid-template"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The services/molly_socket sops secret is now just the raw VAPID private key (the bare 43-character output of 'mollysocket vapid gen') instead of a pre-formatted systemd environment file. A sops template (sops.templates, same mechanism the makemkv config uses) wraps it into MOLLY_VAPID_PRIVKEY=... at activation; the rendered file is root-owned under /run/secrets/rendered/ and never enters the nix store.
Post-deploy: set the secret value in defiant-services.yaml to the bare key (no MOLLY_VAPID_PRIVKEY= prefix), push the secrets repo, 'npins update secrets', then deploy defiant. The Molly linking procedure in the module header now sources /run/secrets/rendered/mollysocket.env instead of the raw secret path.