NixOS Module System | 152 Members | |
| 31 Servers |
| Sender | Message | Time |
|---|---|---|
| 19 Dec 2025 | ||
| the nixos config being built might also end up in the nix store, so plain text secret string options are also a bad idea | 02:52:27 | |
| I would also recommend to construct ExecStart from a list for proper tokenization | 02:52:47 | |
| so escapeShellArgs or escapeSystemdExecArgs, the plural versions | 02:53:00 | |
literalExpression gets used in e.g. defaultText or exampleText to render the string as nix code without evaluating it | 02:53:37 | |
| it gets rendered in place of the actual default or example value | 02:53:49 | |
| which might be a reference to something else | 02:54:06 | |
regarding this, my plan is to create a raw secret option as well as a secretFile option (where the latter takes precedence), just to keep options open for users. But I'll use a regular str for both to avoid secret paths getting copied to the store. | 02:57:58 | |
| the raw secret string option is a bad idea | 02:58:32 | |
| but it's fine if used with sopsnix right? | 02:58:59 | |
| they pass files | 02:59:24 | |
| not strings | 02:59:25 | |
| i have not yet setup/learned how sopsnix works, so I am unsure tbh | 02:59:31 | |
| agenix/sopsnix encrypt and pass files | 02:59:42 | |
| i see, okay thanks | 02:59:57 | |
| then ill re-evaluate how i go about this. but thanks for the advice regardless! | 03:00:17 | |
| 08:08:40 | ||
| 08:25:17 | ||
okay, i've been working on the PR for the nixos/bore module, but I'm at a bit of a roadblock when it comes to nixos tests. Since bore local requires a connection to a remote proxy server (i.e. "bore.pub"), should the nixos tests really be connecting to it to verify functionality? Rather, how does networking work with the test suite? Or should I only run tests for the server variant, which simply needs to check if it can listen on 0.0.0.0:<specified port>? | 20:59:24 | |
| actually i think i might be able to set up a server and a local proxy on the same machine that just interact with each other | 21:14:52 | |
| 20 Dec 2025 | ||
| if anyone has free time, could you skim over this PR and see if things look fine? https://github.com/NixOS/nixpkgs/pull/472353 I'm hoping to ask some non-reviewers before I post in the Nixpkgs Review Requests, just so I can minimize the number of cycles I approach reviewers, who might be busy. Thanks in advance! | 02:39:01 | |
| * if anyone has free time, could you skim over this PR and see if things look fine? https://github.com/NixOS/nixpkgs/pull/472353 I'm hoping to ask some non-reviewers before I post in the Nixpkgs Review Requests channel, just so I can minimize the number of cycles I approach reviewers, who might be busy. Thanks in advance! | 02:39:10 | |
| 8 Feb 2024 | ||
| 10:38:02 | ||
| 15 Feb 2024 | ||
| 19:15:14 | ||
| 16 Feb 2024 | ||
| 14:56:15 | ||
| 14:59:24 | ||
| I recently stumbled upon similar issue when working on home-manager. https://discourse.nixos.org/t/is-it-possible-to-define-systemd-services-in-a-submodule/39538/5 The idea is that enabling https://nix-community.github.io/home-manager/options.xhtml#opt-programs.bash.enableCompletion should set I think that module system is missing an option to pass config options recursively up to all ancestors. | 15:06:01 | |
My idea is that nixos config could have a property extraNixosChildConfig and in home-manager bash module I could set _recurseAncestors = { extraNixosChildConfig = { environment.pathsToLink = [ ... ]; }; }. | 15:07:22 | |
| wdyt? | 15:07:26 | |
* My idea is that nixos config could have a property extraNixosChildConfig that gets merged with the rest of the config and in home-manager bash module I could set _recurseAncestors = { extraNixosChildConfig = { environment.pathsToLink = [ ... ]; }; }. | 15:07:44 | |
* My idea is that nixos config could pick up extraNixosChildConfig from childs and merge it with the rest of the config and in home-manager bash module I could set _recurseAncestors = { extraNixosChildConfig = { environment.pathsToLink = [ ... ]; }; }. | 15:08:21 | |