mirror of
https://github.com/NixOS/nixpkgs.git
synced 2024-11-23 14:11:36 +00:00
56a7bc05e1
The `keys.target` is used to indicate whether all NixOps keys were successfully uploaded on an unattended reboot. However this can cause startup issues e.g. with NixOS containers (see #67265) and can block boots even though this might not be needed (e.g. with a dovecot2 instance running that doesn't need any of the NixOps keys). As described in the NixOps manual[1], dependencies to keys should be defined like this now: ``` nix { systemd.services.myservice = { after = [ "secret-key.service" ]; wants = [ "secret-key.service" ]; }; } ``` However I'd leave the issue open until it's discussed whether or not to keep `keys.target` in `nixpkgs`. [1] https://nixos.org/nixops/manual/#idm140737322342384 |
||
---|---|---|
.. | ||
administration | ||
configuration | ||
development | ||
installation | ||
release-notes | ||
.gitignore | ||
default.nix | ||
Makefile | ||
man-configuration.xml | ||
man-nixos-build-vms.xml | ||
man-nixos-enter.xml | ||
man-nixos-generate-config.xml | ||
man-nixos-install.xml | ||
man-nixos-option.xml | ||
man-nixos-rebuild.xml | ||
man-nixos-version.xml | ||
man-pages.xml | ||
manual.xml | ||
README | ||
shell.nix |
To build the manual, you need Nix installed on your system (no need for NixOS). To install Nix, follow the instructions at https://nixos.org/nix/download.html When you have Nix on your system, in the root directory of the project (i.e., `nixpkgs`), run: nix-build nixos/release.nix -A manual.x86_64-linux When this command successfully finishes, it will tell you where the manual got generated.