tristan/nixinate
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity

Add support for hermetic remote builds #20

Merged
MatthewCroughan merged 1 commit from mc/hermetic-remote into master 2022-05-30 18:53:20 +00:00
Conversation 0 Commits 1 Files changed 3 +62 -11
MatthewCroughan commented 2022-05-29 16:01:53 +00:00 (Migrated from github.com)
Copy link

A hermetic remote rebuild is when Nixinate sends a specific Nix binary to the remote first, then uses it when activating a system closure, rather than using the Nix that is already on the remote. This is defaulted to false for the time being, as the bandwidth usage can be high. This allows users to avoid the need to bootstrap the remote first by enabling flakes on the remote Nix binary.

A hermetic remote rebuild is when Nixinate sends a specific Nix binary to the remote first, then uses it when activating a system closure, rather than using the Nix that is already on the remote. This is defaulted to false for the time being, as the bandwidth usage can be high. This allows users to avoid the need to bootstrap the remote first by enabling flakes on the remote Nix binary.
Kranzes (Migrated from github.com) requested changes 2022-05-29 17:04:34 +00:00
flake.nix
@ -18,1 +18,4 @@
overlay = final: prev: {
nixinate = {
nix = prev.pkgs.writeShellScriptBin "nix"
''${final.nixVersions.unstable}/bin/nix --experimental-features "nix-command flakes" "$@"'';
Kranzes (Migrated from github.com) commented 2022-05-29 17:04:22 +00:00
Copy link

You should avoid using Unstable here. Since 2.4 flakes are supported.

You should avoid using Unstable here. Since 2.4 flakes are supported.
MatthewCroughan (Migrated from github.com) reviewed 2022-05-29 17:31:36 +00:00
flake.nix
@ -18,1 +18,4 @@
overlay = final: prev: {
nixinate = {
nix = prev.pkgs.writeShellScriptBin "nix"
''${final.nixVersions.unstable}/bin/nix --experimental-features "nix-command flakes" "$@"'';
MatthewCroughan (Migrated from github.com) commented 2022-05-29 17:31:36 +00:00
Copy link

Evaluation time is getting better with Nix releases, so I'd rather use unstable, since 2.4 is pretty slow. Also, there are some determinism issues with lockfile generation that I'd prefer to avoid, by using the latest.

Evaluation time is getting better with Nix releases, so I'd rather use unstable, since 2.4 is pretty slow. Also, there are some determinism issues with lockfile generation that I'd prefer to avoid, by using the latest.
Sign in to join this conversation.
Reviewers
No reviewers
Kranzes
Labels
Clear labels   
bug

Something isn't working

  
documentation

Improvements or additions to documentation

  
duplicate

This issue or pull request already exists

  
enhancement

New feature or request

  
good first issue

Good for newcomers

  
help wanted

Extra attention is needed

  
invalid

This doesn't seem right

  
question

Further information is requested

  
wontfix

This will not be worked on

No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tristan/nixinate#20
No description provided.
Delete branch "mc/hermetic-remote"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?