README: include sha256 of the expected release tarball
Advantages of including the SHA256: (i) removes the impurity of the tarball contents being changed (ii) if sha256 is not included, then each nixops deploy triggers a re-download of the tarball Here's how to get the expected hash: $ nix-prefetch-url --unpack 'https://gitlab.com/simple-nixos-mailserver/nixos-mailserver/-/archive/v2.2.0/nixos-mailserver-v2.2.0.tar.gz' unpacking... [0.0 MiB DL] path is '/nix/store/dwg8xlfnlw7mhr4cjk1viwmm0b249b74-nixos-mailserver-v2.2.0.tar.gz' 0gqzgy50hgb5zmdjiffaqp277a68564vflfpjvk1gv6079zahksc
This commit is contained in:
parent
c2ca4d1bb0
commit
2c59de8dcb
1 changed files with 4 additions and 1 deletions
|
@ -67,7 +67,10 @@ See the [mailing list archive](https://www.freelists.org/archive/snm/)
|
|||
{ config, pkgs, ... }:
|
||||
{
|
||||
imports = [
|
||||
(builtins.fetchTarball "https://gitlab.com/simple-nixos-mailserver/nixos-mailserver/-/archive/v2.2.0/nixos-mailserver-v2.2.0.tar.gz")
|
||||
(builtins.fetchTarball {
|
||||
url = "https://gitlab.com/simple-nixos-mailserver/nixos-mailserver/-/archive/v2.2.0/nixos-mailserver-v2.2.0.tar.gz";
|
||||
sha256 = "0gqzgy50hgb5zmdjiffaqp277a68564vflfpjvk1gv6079zahksc";
|
||||
})
|
||||
];
|
||||
|
||||
mailserver = {
|
||||
|
|
Loading…
Reference in a new issue