diff options
| author | Roman Melnikov | 2024-01-10 09:33:11 +0100 |
|---|---|---|
| committer | GitHub | 2024-01-10 09:33:11 +0100 |
| commit | 1776009f1f3fb2b5d236b84d9815f2edee463a9b (patch) | |
| tree | b6d191da2c2cdbbf0ee945c210336e91a62b845b | |
| parent | b709d63debafce9f5645a5ba550c9e0983b3d1f7 (diff) | |
| parent | 3f91911972d4b1576b23e42feec9804bdcfb7fe0 (diff) | |
Merge pull request #252 from SuperSandro2000/patch-1
Remove note about unstable nix version
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -54,7 +54,7 @@ There is a built-in feature to prevent you making changes that might render your ### Overall usage -`deploy-rs` is designed to be used with Nix flakes (this currently requires an unstable version of Nix to work with). There is a Flake-less mode of operation which will automatically be used if your available Nix version does not support flakes, however you will likely want to use a flake anyway, just with `flake-compat` (see [this wiki page](https://nixos.wiki/wiki/Flakes) for usage). +`deploy-rs` is designed to be used with Nix flakes. There is a Flake-less mode of operation which will automatically be used if your available Nix version does not support flakes, however you will likely want to use a flake anyway, just with `flake-compat` (see [this wiki page](https://nixos.wiki/wiki/Flakes) for usage). `deploy-rs` also outputs a `lib` attribute, with tools used to make your definitions simpler and safer, including `deploy-rs.lib.${system}.activate` (see later section "Profile"), and `deploy-rs.lib.${system}.deployChecks` which will let `nix flake check` ensure your deployment is defined correctly. |