Conversation
|
Any chance to have this considered? @infinisil |
|
There's a longer discussion on this in #325793 |
| # following the advice from https://github.com/direnv/direnv/wiki/.envrc-Boilerplate | ||
| # load developer's own local .env | ||
|
|
||
| dotenv_if_exists || direnv status # https://direnv.net/man/direnv-stdlib.1.html |
There was a problem hiding this comment.
What if I want to load variables before use nix that influence how Nix will operate?
There was a problem hiding this comment.
I don't know... maybe you shouldn't? that's probably the bad "side effects" and can give surprises.
I think the upstream decides to remove the .envrc after all. So I guess, we are gonna be back to the previous status quo.
I actually wouldn't mind much, and started to commit .envrc in other projects after I saw the wki page on direnv...
There was a problem hiding this comment.
Setting something like NIXPKGS_ALLOW_UNFREE could be useful to some before Nix is invoked on a per-project basis. This does not seem weird.
Description of changes
.envrc: add dotenv_if_exists
As a developer, I would like to use my local .env when working on a new PR.
Following some advice from: https://github.com/direnv/direnv/wiki/.envrc-Boilerplate
Things done
nix.conf? (See Nix manual)sandbox = relaxedsandbox = truenix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/)Add a 👍 reaction to pull requests you find important.