Age | Commit message (Collapse) | Author | Files | Lines |
|
fixes "mount"
(cherry picked from commit be0a6b0dd6b72667a930a8e26bf4ae9e99b311a5)
|
|
This avoids computing the prio more than necessary.
The test evaluates to the same derivation hash.
(cherry picked from commit 7438f4e0de4f41a562c4292a035f406129208bfd)
|
|
Signed-off-by: Sefa Eyeoglu <contact@scrumplex.net>
(cherry picked from commit 58f091d5ac33943664b7567d68a6777ddc775df1)
|
|
The --rsyncable option changes the behavior of gzip/zstd so that the
resulting files can be incrementally backed up easily. Tools like Borg,
rsync and xdelta can make use their deduplication/diff mechanisms more
easily.
In my local testing, this resulted in a 2% size increase for backup
files.
Signed-off-by: Sefa Eyeoglu <contact@scrumplex.net>
(cherry picked from commit 40c3d65bdff49b818073d7c92cf0ec6d7fab2bba)
|
|
The sshKey options do not need to be a valid path at build time. Using
string instead allow use case when the path is not known at build time
such as when using systemd credentials (e.g. `sshKey =
"\${CREDENTIALS_DIRECTORY}/zfs-replication_ed25519";`).
(cherry picked from commit e98fd99eb3a6c81a18ea9494f684764e75315e8f)
|
|
(cherry picked from commit 19af28537bb59c849a666fce27e15d1f33fb03ee)
|
|
|
|
nixos/restic: fix #264696 and add a regression test
|
|
* leaving PrivateUsers=true appears to break when using zfs-2.2.0
|
|
Make sure that preStart and postStop are included in all cases when they are nonempty.
|
|
As described in the release lifecycle docs from postgresql[1], v11 will
stop receiving fixes as of Nov 9 2023. This means it's EOL throughout
the entire lifetime of 23.11, so let's drop it now.
A lot of examples are also referencing postgresql_11. Where it's
sensible, use postgresql_15 as example now to avoid confusion.
This is also handy because the LLVM 16 fix for postgresql is not
available for postgresql 11 ;-)
[1] https://www.postgresql.org/support/versioning/
|
|
borgmatic: fix deprecation warning check failed
|
|
|
|
This has been deprecated since 2021, so all users should have seen the
warning and migrated by now.
|
|
nixos/backups/restic: handle cases when both dynamicFileFrom and paths are set
|
|
nixos/bacula: fix postgresql config and remove unneeded quotation marks
|
|
Fix descriptions that don't account for (1) the "Whether to enable"
prefix or (2) the automatically added trailing dot.
|
|
|
|
Co-authored-by: Lin Jian <me@linj.tech>
|
|
nixos/btrbk: fix btrfs path for passwordless execution
|
|
|
|
|
|
nixos/duplicati: add package option
|
|
and use in test
|
|
|
|
|
|
|
|
Also, add a test to verify that it works.
This change also removes the part of custom package test that verifies
that the correct paths are provided. This is already tested by restore
tests.
Before this change, setting both paths and dynamicFileFrom would cause
paths to be silently ignored. Making that actually apply the obvious
interpretation seems to me to be strictly better than prohibiting the
two from being set at the same time.
|
|
The module falsely disabled postgresql completely when the bacula-sd was not enabled.
Quotation marks are not necessary and only useful in `name` fields.
|
|
tarsnap: add package option
|
|
treewide: use optionalString instead of 'then ""'
|
|
|
|
|
|
|
|
|
|
Fixes the extraCompactArgs introduced with #224072 as the variable
currently isn't added to the script's environment.
|
|
|
|
|
|
To reduce the danger of accidentally exposing sensitive files processed
by a restic backup to other services/users, enable the `PrivateTmp=`
feature of restic service units, which provides a per service isolation
of `/tmp` and `/var/tmp`.
Co-authored-by: Daniel Nagy <danielnagy@posteo.de>
|
|
|
|
|
|
|
|
|
|
sanoid/syncoid: Add package options
|
|
Allows changing the sanoid package to be used for these services.
|
|
nixos/restic: generalize cache configuration
|
|
btrbk: Use sudo or doas based on configuration
|
|
The restic repository cache location defaults to ~/.cache/restic when
not overwritten either by the --cache-dir command line parameter or the
universal RESTIC_CACHE_DIR environment variable.
Currently, the --cache-dir variable is set to only some restic commands,
but, e.g., not to the unit's preStart command for the module's
initialize option. This results in two distinct cache locations, one at
~/.cache/restic for the initialize commands and one at the configured
--cache-dir location for the restic backup command.
By explicitly setting RESTIC_CACHE_DIR for the unit, only one cache at
the correct location will be used.
https://restic.readthedocs.io/en/v0.15.1/manual_rest.html#caching
|
|
nixos/borgmatic: Allow defining multiple configurations
|
|
|