Sender | Message | Time |
---|---|---|
8 May 2025 | ||
That would be the folder of the consuming flake, because the imported home manager module should provide a nix-rebuild command which does home-manager switch --flake ${flakefolder}#main . flakefolder is the variable I want to pass downstream. | 11:40:11 | |
* That would be the folder of the consuming flake, because the imported home manager module should provide a nix-rebuild command which does home-manager switch --flake ${flakefolder}#main (and other corporate stuff). flakefolder is the variable I want to pass downstream. | 11:40:38 | |
you would have something like
| 11:45:12 | |
(note: untested) | 11:45:29 | |
and then in your regular module you would set
| 11:45:49 | |
this way the module works just like any other option you already have in home-manager | 11:48:58 | |
Ah I see, thank you. | 11:51:22 | |
12:00:10 | ||
So that would result in something like this?
| 12:39:13 | |
9 May 2025 | ||
03:23:08 | ||
10 May 2025 | ||
19:44:36 | ||
19:53:11 | ||
23:32:18 | ||
12 May 2025 | ||
I have a bunch of eg.
in the flake for my systems, applied with But recently, github rate limits have been hitting me on like 100% of my | 16:35:42 | |
If I could set an access token on githubusercontent, it would work (eg. as in curl "https://patch-diff.githubusercontent.com/raw/NixOS/nixpkgs/pull/386205.patch?access_token=$GITHUB_TOKEN" ), but I have no idea how to configure that without exposing the token directly in my flake.nix, which is a public file | 16:39:36 | |
* I have a bunch of eg.
in the flake for my systems, applied with But recently, github rate limits have been hitting me on like 100% of my | 16:41:03 | |
In reply to @gsaurel:laas.frfor flake inputs you're in luck, you can set the access-tokens nix option | 17:04:03 | |
oh wait hmmm | 17:04:25 | |
yeah i posted too quick and didn't notice you're using https on a github url... | 17:06:19 | |
I tried access-tokens = github.com=ghp_… patch-diff.githubusercontent.com=ghp_… , but it didn't work, and I found in the doc that it is like only for specific to github/gitlab things, so this probably won't work with a random thing | 17:08:16 | |
tbh, i'm mostly surprised this even works. having non-pinnable https inputs is a surefire way to make your old flake revisions non-reproducible | 17:10:52 | |
it'll fail the flake.lock check forcing you to update | 17:11:36 | |
13 May 2025 | ||
08:51:52 | ||
09:21:46 | ||
09:25:18 | ||
14:24:05 | ||
14 May 2025 | ||
03:52:40 | ||
04:09:54 | ||
11:49:44 | ||
17:16:20 |