Update README.md

Author: n0099

README.md

@@ -364,7 +364,20 @@ e.g. inside your `flake.nix` file:
    When the `age.secrets` attribute set contains a secret, the `agenix` NixOS module will later automatically decrypt and mount that secret under the default path `/run/agenix/secret1`.
    Here the `secret1.age` file becomes part of your NixOS deployment, i.e. moves into the Nix store.
 
-6. Reference the secrets' mount path in your config:
+   You may also generate them based on the `secrets.nix` file with no extra options:
+   ```nix
+   { lib, ... }:
+
+   {
+     age.secrets =
+       lib.genAttrs (lib.map (lib.removeSuffix ".age") (lib.attrNames (import ./secrets.nix)))
+         (name: {
+           file = ./${name}.age;
+         });
+   }
+   ```
+
+7. Reference the secrets' mount path in your config:
    ```nix
    {
      users.users.user1 = {
@@ -375,11 +388,11 @@ e.g. inside your `flake.nix` file:
    ```
    You can reference the mount path to the (later) unencrypted secret already in your other configuration.
    So `config.age.secrets.secret1.path` will contain the path `/run/agenix/secret1` by default.
-7. Use `nixos-rebuild` or [another deployment tool](https://wiki.nixos.org/wiki/Applications#Deployment") of choice as usual.
+8. Use `nixos-rebuild` or [another deployment tool](https://wiki.nixos.org/wiki/Applications#Deployment") of choice as usual.
 
    The `secret1.age` file will be copied over to the target machine like any other Nix package.
    Then it will be decrypted and mounted as described before.
-8. Edit secret files:
+9. Edit secret files:
    ```ShellSession
    $ agenix -e secret1.age
    ```