In reply to @ultranix:matrix.org
stringPassword = "${builtins.readFile ./secrets/password}"

In reply to @pachumicchu:myrdd.info
Well if you are doing something like this, I'm pretty sure that secret will end up in the nix store at some point

In reply to @ultranix:matrix.org
but also, there's a lot of configuration ini's that still use string keys within config files

In reply to @blaggacao:matrix.org
I now only need a strawman to submit the patch.

In reply to @teutat3s:pub.solar
I’d volunteer, will submit it later today

I have a few warnings when doing nix flake check:

warning: unknown experimental feature 'ca-references'
warning: unknown flake output 'homeModules'
warning: unknown flake output 'devshellModules'
warning: unknown flake output 'pkgs'
warning: unknown flake output 'outputsBuilder'
warning: unknown flake output 'homeConfigurationsPortable'

I do not use those (besides pkgs), is that a problem in digga then?

In reply to @ultranix:matrix.org
by the way, i still found a lot of use for git-crypt. I use it to encrypt string secrets in public repositories

In reply to @ultranix:matrix.org
by the way, i still found a lot of use for git-crypt. I use it to encrypt string secrets in public repositories

hello, im trying to update to 21.11 but when i change the pinned version of nixpkgs i get this error:

`error: value is null while a set was expected

   at /nix/store/rlgzhd7yf0hna1drzdjnia06jz816y03-source/overlays/nix-patched.nix:5:17:

        4|
        5|   nixUnstable = prev.nixUnstable.overrideAttrs (o: {
         |                 ^
        6|     patches = (o.patches or [ ]) ++ [

(use '--show-trace' to show detailed location information) `

You could try

nix flake lock --update-input digga

and maybe after that just:

nix flake update

This will update the flake.lock for all inputs

hmmmm, not quite? this is the error i get now. seems like digga didn't update?

` trace: warning: You are accessing a deprecated item of the digga lib. Please update timely, it will be remove soon.

trace: warning: Deprecated Function: lib.importModules.

Use lib.importExportableModules instead to set exportedModules option

error: ERROR: The externalModules option has been removed. Any modules that should be exported should be defined with the exportedModules option and all other modules should just go into the modules option. (use '--show-trace' to show detailed location information) `

hmmmm, not quite? this is the error i get now. seems like digga didn't update?

`trace: warning: You are accessing a deprecated item of the digga lib. Please update timely, it will be remove soon.

trace: warning: Deprecated Function: lib.importModules.

Use lib.importExportableModules instead to set exportedModules option

error: ERROR: The externalModules option has been removed. Any modules that should be exported should be defined with the exportedModules option and all other modules should just go into the modules option. (use '--show-trace' to show detailed location information)`

hmmmm, not quite? this is the error i get now. seems like digga didn't update?

`trace: warning: You are accessing a deprecated item of the digga lib. Please update timely, it will be remove soon.

trace: warning: Deprecated Function: lib.importModules.

Use lib.importExportableModules instead to set exportedModules option

error: ERROR: The externalModules option has been removed. Any modules that should be exported should be defined with the exportedModules option and all other modules should just go into the modules option. (use '--show-trace' to show detailed location information)`