Zhaofeng Li

[Here](https://github.com/otavio/nix-config/blob/bb3b88cab799787f3023b9a1f676c482273e82cc/lib/default.nix#L18-L24) you are just extracting the `system` and `modules` from the `nixosSystem`, and Colmena doesn't know what you passed in its `specialArgs`.

That's an interesting idea! I think an easy way to implement this is with a list of scripts (`deployment.checkScripts` maybe?) that are run on the target machine after the configuration...

Yeah, I agree that it doesn't lend to composability (see #55). Having it as part of the module system is a bit tricky to get right, and #56 was one...

It's a chicken-and-egg problem, because in order to get `deployment.nixpkgs` from a node's config the first place, you need a nixpkgs for its evalModules implementation.

One way is to have a list of secret files saved somewhere, and on activation perform a diff and delete those that are no longer in the new configuration.

> it seems that some packages are also being used This is no longer the case in the main branch, where we now just evaluate the `.drvPath`s of system profiles...

I don't think it's possible to evaluate the entire configuration in JSON, since many parts of the configuration depend on lazy evaluation. In this case, the `message` attribute of the...

Note that now there is also a new channel at [#colmena:nixos.org](https://matrix.to/#/#colmena:nixos.org) for Colmena-specific stuff.

I don't have any plans of implementing provisioning directly in Colmena since I'd like to keep it lean - closer to morph than to NixOps. That being said, @justinas's suggestion...

To install onto bare-metal hosts from Colmena, I've been using [this script](https://gist.github.com/zhaofengli/e986fa7688d6c16872b86c6ae6215c9b) in the past weeks. It requires you to have already finished partitioning, mounted everything onto `/mnt`, and retrieved...