From 1e94d11ce026a057677733e05aa99366df342c91 Mon Sep 17 00:00:00 2001 From: Jo Date: Thu, 4 Sep 2025 14:19:17 +0200 Subject: [PATCH] =?UTF-8?q?=F0=9F=93=9D=20Improve=20README=20readability?= =?UTF-8?q?=20and=20completeness?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index df3a877..6f0b954 100644 --- a/README.md +++ b/README.md @@ -43,6 +43,7 @@ Secrets are managed by the [sops-nix](https://github.com/Mic92/sops-nix) nixos/h - General secrets are stored within the `secrets` directory. - System specific secrets are stored within their respective `systems///secrets` directory. +- User secrets are stored within their respective `homes///secrets` directory. The following command may be used to convert the SSH host key of a new machine to an age key: @@ -66,7 +67,7 @@ You may also encrypt arbitrary binary formats, like .cfg, using the following co nix-shell -p sops --run "sops -e original_file.cfg > secrets/encrypted_file.cfg" ``` -Lastly, when adding new systems, make sure to update any required secret files with the following command: +Finally, when adding new systems, make sure to update any required secret files with the following command: ```sh nix-shell -p sops --run "sops updatekeys secrets/example.yaml" @@ -117,7 +118,7 @@ Some of my future goals for this flake are: - Further refining my usage of the Nix language, through language best-practices and CLI dev tools. ## 🏗️ Structure -The structure this flake aims to build on is relatively simple to grasp. +This flake follows an opinionated directory structure, described below. ``` flake.nix --> The flake.