aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* README: explain that extraOptions are separate argumentstv45 hours1-1/+2
|
* flake: pass populate to krops, describe using krops from a flaketv45 hours2-1/+35
| | | | | | | | | | | pkgs/krops takes populate as an argument, which nixpkgs doesn't provide, so evaluating any of the flake's lib attributes from pkgs/krops fails. The flake passes its own populate. The README describes using krops from a flake: writeDeploy and the other functions from lib.<system>, evalSource and mkTarget from krops' lib directory, and deploying with nix run --impure, because krops' lib evaluates <nixpkgs/lib>, environment variables, and /etc/hostname.
* krops writeDeploy: pass --no-flake if /etc/nixos/flake.nix existstv45 hours3-3/+17
| | | | | | | | | | | nixos-rebuild deploys /etc/nixos/flake.nix instead of NIX_PATH if that file exists, so deploying anything but a flake fails on such targets. Without writeDeploy's flake parameter, nixos-rebuild gets --no-flake if /etc/nixos/flake.nix exists on the build target. nixos-rebuild versions predating flakes neither know --no-flake nor look for that file, so they don't get it. The deploy VM test covers targets with and without that file.
* krops writeDeploy: pass --use-remote-sudo only with a separate build targettv45 hours5-12/+85
| | | | | | | | | | | | For targets using sudo, writeDeploy runs nixos-rebuild on the target via sudo, so --use-remote-sudo has no effect there. It only matters when nixos-rebuild runs on a separate build target and activates the system on the target, so writeDeploy passes it only then. A new VM test, deploy, runs writeDeploy with a stand-in for nixos-rebuild, which records the user it runs as, NIX_PATH, and its arguments, for deploying flakes and other sources, with and without a separate build target, to every kind of target.
* populate: add prunetv47 hours4-7/+115
| | | | | | | | | | | | | | | | | | | Populate never removes what it delivered for sources that aren't configured anymore. For flake and flake-input sources, that keeps their garbage collector roots, so what they delivered never gets collected. With prune, populate removes everything from the target directory that isn't a source, except .populate, after syncing the sources. It also removes the roots in .populate/flake-inputs of names that aren't flake or flake-input sources, and uploads left behind by interrupted runs. Pruning is opt-in, because the target directory may contain other things worth keeping, or be shared by deployments with different sources. writeDeploy, writeTest, and writeCommand pass prune on to populate. A feature scenario deploys sources, deploys fewer without pruning, then with pruning, and checks that the removed sources' entries and roots are gone, while the remaining sources and .populate stay.
* tests: add NixOS VM tests for populatetv2 days6-0/+930
| | | | | | | | | | | | | | | | | tests/default.nix provides one VM test per source type, and one for features spanning sources. Each test runs scenarios from tests/scenarios.nix, which cover every combination of a source type's options, deployed to the deploying machine itself, to a remote target as root, and to a remote target using sudo. A scenario prepares the target directory, deploys, checks the result, and deploys and checks again. Scenarios expecting populate to fail check its error message, or check at evaluation time if populate is expected not to evaluate. The deploying machine creates fixtures using tests/fixtures.sh and serves them via HTTP and git daemon, so flakes can be fetched on the target without further network access. Checks evaluate delivered flakes without network access to the fixtures after collecting garbage, so they verify that the delivered store paths are complete and rooted.
* populate: stop the ssh master only if there is onetv2 days1-1/+4
| | | | | | | Populate ends by stopping the ssh master, which fails if no source started one, e.g. for local targets, which populate doesn't reach via ssh. Populate then exits with ssh's exit status, though all sources got delivered. Populate now checks for a master first.
* populate flake-input: support subdirectories named in URLstv2 days1-7/+41
| | | | | | | | Depending on the version of Nix, flake references and lock entries name the subdirectory containing a flake either as attribute dir or as query parameter dir of their URL. fetchTree supports neither, so populate looks for both: it takes the subdirectory from either, from the locked or the original reference, and removes both before fetching.
* populate flake: support fetchOnTargettv2 days3-31/+216
| | | | | | | | | | | | | | | | | | With fetchOnTarget, the target fetches the flake's inputs using the arguments recorded in the lock file, like it does for flake-input sources. The flake itself has no lock entry, so the target fetches it by its locked reference, unless that refers to the deploying machine, e.g. a path or a Git work tree. Then the flake's tree gets transferred using rsync and added to the target's store using nix-store --add-fixed, which yields the same store path as on the deploying machine, because flake store paths are content-addressed by their NAR hash. Adding paths like this needs neither signatures nor a trusted user, so this works for targets using sudo. The transfer gets skipped if the target's store has the flake already, and populate fails if the added path differs from the expected one. rsync' gets a filterFiles option, so the flake's tree gets transferred without applying .rsync-filter files, which would change it.
* populate: add flake-input source typetv2 days3-46/+90
| | | | | | | The flake-input source type delivers an input of a flake, as recorded in the flake's lock file, and the flake source type delivers the flake itself. fetchOnTarget belongs to flake-input, because only a locked input can be fetched on the target.
* krops writeDeploy: deploy generated flakestv2 days1-1/+12
| | | | | The flake parameter names a source. If the source draws inputs from other sources, its generated flake gets deployed.
* krops writeDeploy: add flake parametertv2 days2-2/+18
| | | | | | With flake set, nixos-rebuild deploys that flake from the build target's source directory, with flakes enabled for the command. The deployment fails with an error message unless Nix on the build target supports flakes.
* populate: generate flakes for inputs drawn from sourcestv2 days3-5/+222
| | | | | | | | | | | | | | For each source that draws inputs from other sources, populate generates a flake in .populate/flakes/<name>, which re-exports the outputs of the source's flake with those inputs drawn from the other sources. The source itself stays as it is, so NIX_PATH still refers to it. Generated flakes refer to each other's generated flakes, so a source's own declarations apply wherever it gets drawn from, and get generated in dependency order. Evaluation fails for sources drawing inputs from missing sources, from themselves, or from each other. Generated flakes get locked on every run, and get removed once their sources no longer draw inputs from other sources.
* lib: add flakeFollowstv2 days1-0/+14
| | | | | flakeFollows lists the inputs a source draws from other sources, with the paths of nested inputs flattened.
* populate flake: add fetchOnTargettv2 days3-23/+97
| | | | | | | | | | With fetchOnTarget, the target fetches the input and its own inputs itself, using fetchTree with the arguments recorded in the flake's lock file. Only nix flake metadata runs on the deploying machine, so the inputs get downloaded once, by the target. This needs Nix with flake support on the target, which populate checks before fetching. Because nothing gets copied, this also works for targets using sudo.
* lib shell: add requireFlakestv2 days1-0/+14
| | | | | | Shell code that enables flakes for the Nix commands following it, and fails with an error message naming the host and the Nix version found, unless Nix supports flakes.
* populate: add flake source typetv2 days3-1/+163
| | | | | | | | | | | | Deliver a flake, or one of its locked inputs, to the target: archive the flake locally, copy the selected input together with its own inputs into the target's store, and link it at the target path, registered as garbage collector root. The result can be used in NIX_PATH as well as by flakes evaluated on the target, without network access. nix copy runs with a separate ssh wrapper without the control socket, because Nix waits for its LocalCommand, which may not run over a multiplexed connection.
* populate: export TMPDIRtv2 days1-0/+1
| | | | | | | Each job and the ssh wrapper run as separate scripts, which only see TMPDIR if it's exported. Without TMPDIR in the caller's environment, jobs fail, and the ssh wrapper's control socket ends up at the root directory.
* populate backup: fix error messagetv2 days1-1/+1
|
* populate: derive socket name from target hosttv2026-01-011-2/+2
|
* populate: use ssh control socket1.30.0tv2025-12-091-6/+12
|
* populate use singular tmpdirtv2025-12-091-24/+22
| | | | | | | | Set TMPDIR to a fresh, private top-level temporary directory, and run each job in a separate subdirectory beneath it. TMPDIR remains shared across all jobs, allowing reuse of resources like ssh control sockets.
* populate pass{,age}: use $pass_outtv2025-12-091-9/+9
|
* populate pipe: use rsynctv2025-12-091-2/+10
| | | | Generate a reproducible output to transmit it only if it has changed.
* populate passage: rename loop variablestv2025-04-091-6/+7
|
* populate rsync': reduce verbositytv2025-04-091-1/+2
|
* populate: add passage source type1.29.0tv2024-01-113-1/+82
|
* init flake.nixlassulus2023-07-222-0/+56
|
* Merge pull request #38 from fuu0/patch-1Lassulus2023-04-081-1/+1
|\ | | | | Update README.md to fix broken link with infos to the `target` attribute
| * Update README.mdfuu02023-04-081-1/+1
| | | | | | fix broken link to with infos to the `target` attribute
* | populate pass: calculate hash for each symlink1.28.2lassulus2023-03-131-1/+9
| | | | | | | | | | this fixes folders with symlinks not getting updated if the symlinked file is in another subfolder of the pass repo
* | rebuild: set NIX_PATH like everywhere else1.28.1tv2022-09-071-3/+2
| |
* | withNixOutputMonitor: run shell with know Nix pathtv2022-09-071-2/+3
| |
* | runShell: admit non-posix-compatible shellstv2022-09-071-1/+4
| |
* | krops writeDeploy: add useNixOutputMonitor parameter1.28.0tv2022-08-232-7/+71
| |
* | Merge remote-tracking branch 'prism/master'1.27.0tv2022-07-262-2/+7
|\ \ | |/ |/|
| * krops writeTest: make trace optionallassulus2022-07-262-2/+7
| |
* | krops writeDeploy: add operation parametertv2022-07-162-3/+8
|/
* populate git: remove trailing spaces1.26.3tv2022-02-121-1/+1
|
* populate git: remove non-worktree targettv2022-02-121-0/+5
|
* Merge pull request #35 from erikarvstedt/fix-ssh-port1.26.2tv2021-11-206-55/+78
|\ | | | | target: use default port from SSH config
| * target: use default port from SSH configErik Arvstedt2021-11-203-6/+8
| | | | | | | | | | This is the expected behavior. The SSH config is also implicitly used for other SSH-related settings.
| * populate file: isDerivation -> isStorePath1.26.1tv2021-10-261-2/+2
| |
| * populate file: admit derivations1.26.0tv2021-10-264-8/+25
| |
| * README: transfered -> transferredtv2021-10-261-1/+1
| |
| * README: talk about systemstv2021-10-261-1/+1
| |
| * populate: add rsyncDefaultConfigtv2021-10-261-7/+14
| |
| * runShell/writeCommand: add allocateTTY argumentlassulus2021-10-262-4/+11
| |
| * krops writeDeploy: deprecate fast parameterlassulus2021-10-261-29/+19
| |
| * README: use latest krops version in exampleMatthias Beyer2021-10-261-2/+2
|/ | | | Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
generated by cgit v1.3.1 (git 2.54.0) at 2026-11-13 22:45:15 +0000