hosting/selfhostblocks
1
0
Fork 0
Code Issues Activity

Update README.md

Browse source
This commit is contained in:
Pierre Penninckx 2023-11-19 09:00:37 -08:00 • committed by GitHub
parent 9c121816c9
commit 8abf9e4236
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
examples/homeassistant/README.md
View file

@ -34,7 +34,7 @@ in the `/run/secrets` folder on the VM. We thus need one private key for you to
[`secrets.yaml`](./secrets.yaml) file and one in the VM for it to decrypt the secrets. [`secrets.yaml`](./secrets.yaml) file and one in the VM for it to decrypt the secrets.
Your private key is already pre-generated in this repo, it's the [`sshkey`](./sshkey) file. But when Your private key is already pre-generated in this repo, it's the [`sshkey`](./sshkey) file. But when
creating the VM in the step above, a new private key and its accompanying public key was creating the VM in the step above, a new private key and its accompanying public key were
automatically generated under `/etc/ssh/ssh_host_ed25519_key` in the VM. We just need to get the automatically generated under `/etc/ssh/ssh_host_ed25519_key` in the VM. We just need to get the
public key. public key.
@ -52,6 +52,8 @@ skipped key: got ssh-rsa key type, but only ed25519 keys are supported
age1l9dyy02qhlfcn5u9s4y2vhsvjtxj2c9avrpat6nvjd6rjar3tflq66jtz0 age1l9dyy02qhlfcn5u9s4y2vhsvjtxj2c9avrpat6nvjd6rjar3tflq66jtz0
``` ```
Now, make the `secrets.yaml` file decryptable in the VM.
```bash ```bash
SOPS_AGE_KEY_FILE=keys.txt nix run --impure nixpkgs#sops -- \ SOPS_AGE_KEY_FILE=keys.txt nix run --impure nixpkgs#sops -- \
--config sops.yaml -r -i \ --config sops.yaml -r -i \