The whole system is a derivation itself, a bit like a buildEnv that aggregates all the installed packages and srfvixes, and has an activation script. So this gets built locally, shipped over to the target with scp, the system symlink is replaced and finally the activation script is run. The activation script deals with shutting and starting service and various other impurities.
On Fri, 16 Sep 2016, 21:46 Kevin Cox, <kevin...@kevincox.ca> wrote: > > > On Sep 16, 2016 19:50, "Wilhelm Schuster" <w...@wilhelm.re> wrote: > > Hi, > > I’m trying to use NixOps to deploy onto an existing NixOs instance > (physical server; targetEnv = “none") and was wondering how the system > configuration is applied. Specifically, does my NixOps description of the > server get merged with the local configuration (meaning the one on the > server itself in /etc/nixos/configuration.nix), or does it completely > replace it? > > > It completely replaces it. In general nixops doesn't read anything from > the target server. Everything is built first, then pushed to the target. > The only reason that the state of the target will have any effect is if you > have a runtime program that reads an explicit path. > > _______________________________________________ > nix-dev mailing list > nix-dev@lists.science.uu.nl > http://lists.science.uu.nl/mailman/listinfo/nix-dev >
_______________________________________________ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
