morph
morph copied to clipboard
DBCDK
NixOS deployment tool
PR #96 has already greatly improved working with machines that have differing requirements/architecture, however there is still one use-case that is largely unsupported: Multiple `nixpkgs` versions. From what I understand...
* `network.nixConfig` * `network.runCommand` * `network.lib` * `network.pkgs` (now optional) * `deployment.substituteOnDestination` * `deployment.targetHost` * `deployment.targetUser`
Is there a way to inspect the system of a host given its .nix configuration? Normally I do `nix repl ''` and then I can look at `config`. Now instead...
Hi! Something very strange has happened in one of my deployments. Even though I did not get any errors when using `morph deploy switch`, in the server, one of the...
Building for different architectures on a per deployment base feels not very intuitive. I got it working by setting `network.pkgs` to an instance of nixpkgs with no further configuration while...
Also, users can supply a function for `network.evalConfig` instead of just a path, if desired.
Based on #166. This adds a new argument to `machine`, which is the list of node names to build. This also changes `argsFile` to `argsJSON`, for passing the list of...
This allows using the nix portion of morph, without needing to know implementation details of where the nix expression is. I'm not sure if the attributes exposed there want to...
Currently, the gc-root, if persisted, only contains the hosts selected in the last morph build. It's very common in my workflow to build or deploy a single host for a...