Johan Thomsen

Rebased this with master and revived the code + undrafted the PR. I've use this patch myself for some time and I think it's sad that I need a fork...

@durch Done!

Clarifying: Similar to how default.nix works for the nix cli? To allow for something like `morph build /some/directory`, where /some/directory contains a deployment.nix ?

Right. The only reason I can think of right now is shell-completion ergonomics. If we can implement this while still keeping auto-completion sane for combinations like: `morph deploy switch`, then...

@flokli Thanks for this. We actually thought about that when writing the first versions of morph. One major argument against this is to align with how `nix copy` handles remote...

see also @andrew-d 's comment here: https://github.com/NixOS/nixpkgs/pull/78107#issuecomment-577012848

One problem here is bash completion. Consider `morph deploy examples/default.nix ... switch`. It's impossible to completion suggest multiple file args, while also being able to suggest keyword args like "switch"...

Hi @evrim , Since `nix.autoUpgrade` just runs `nixos-rebuild switch --upgrade`, nixos-rebuild by default will use the NIX_PATH to search for a nixos-config, defaulting to /etc/nixos/configuration.nix. Morph doesn't copy your configuration...

It seems that the 20.03 gnupg module have an eval-dependency on pkgs.pinentry.flavors which doesn't exist in the 19.09 package-set. This effectively mean that you cannot eval 19.09-nixpkgs with 20.03 NixOS-modules...

@leotaku For the record, this demonstrates the nixpkgs/nixos-modules conflict I was referring to: ``` let common = { pkgs, ... }: { environment.systemPackages = [ pkgs.hello ]; fileSystems."/" = {...