| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| | |\ \ \
| | |_|/
| |/| | |
nixos/prometheus: optionally support reloading on config changes
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The new option `services.prometheus.enableReload` has been introduced
which, when enabled, causes the prometheus systemd service to reload
when its config file changes.
More specifically the following property holds: switching to a
configuration (`switch-to-configuration`) that changes the prometheus
configuration only finishes successully when prometheus has finished
loading the new configuration.
`enableReload` is `false` by default in which case the old semantics
of restarting the prometheus systemd service are in effect.
|
| |\| | | |
|
| | |\ \ \
| | |_|/
| |/| | |
code-server: init code-server-module
|
| | | | | |
|
| |\| | | |
|
| | | | | |
|
| |\| | | |
|
| | |\ \ \
| | |_|/
| |/| | |
nixos/ddclient: replace password with passwordFile option
|
| | | | | |
|
| |\| | | |
|
| | | | | |
|
| |\| | | |
|
| | |\ \ \ |
|
| | | | |/
| | |/| |
|
| |\| | | |
|
| | |\| | |
|
| | | |\ \
| | | | |
| | | | | |
python3.pkgs.ihatemoney: 4.2 -> 5.1.1
|
| | | | | | |
|
| |\| | | | |
|
| | |\| | | |
|
| | | | |/
| | |/| |
|
| |\| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
nixos/doc/manual/from_md/release-notes/rl-2111.section.xml
nixos/doc/manual/release-notes/rl-2111.section.md
|
| | |\| | |
|
| | | | |
| | | |
| | | |
| | | | |
...and rename of virtualisation.pathsInNixDB.
|
| | |\| | |
|
| | | |\ \
| | | | |
| | | | | |
nextcloud20: drop
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The version 20 of Nextcloud will be EOLed by the end of this month[1].
Since the recommended default (that didn't raise an eval-warning) on
21.05 was Nextcloud 21, this shouldn't affect too many people.
In order to ensure that nobody does a (not working) upgrade across
several major-versions of Nextcloud, I replaced the derivation of
`nextcloud20` with a `throw` that provides instructions how to proceed.
The only case that I consider "risky" is a setup upgraded from 21.05 (or
older) with a `system.stateVersion` <21.11 and with
`services.nextcloud.package` not explicitly declared in its config. To
avoid that, I also left the `else-if` for `stateVersion < 21.03` which
now sets `services.nextcloud.package` to `pkgs.nextcloud20` and thus
leads to an eval-error. This condition can be removed
as soon as 21.05 is EOL because then it's safe to assume that only
21.11. is used as stable release where no Nextcloud <=20 exists that can
lead to such an issue.
It can't be removed earlier because then every `system.stateVersion <
21.11` would lead to `nextcloud21` which is a problem if `nextcloud19`
is still used.
[1] https://docs.nextcloud.com/server/20/admin_manual/release_schedule.html
|
| |\| | | | |
|
| | |\| | | |
|
| | | |\ \ \ |
|
| | | | | | | |
|
| |\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
* FluidSynth 1.1.11 was kept around as a dependency of some packages
that hadn't yet adjusted to API breakages. All of these packages now
use FluidSynth 2.x, so fluidsynth_1 can be removed. It has been broken
ever since glib was updated to 2.70 and was affected by an unpatched
CVE.
* Refactor expression a bit, use pname instead of name.
* Add changelog entry in case someone was using this downstream
(accidentally?).
Fixes #141508.
Fixes #124624.
|
| |\ \ \ \ \ \
| | |/ / / /
| |/| | | | |
|
| | | | | | | |
|
| |\| | | | | |
|
| | | | | | | |
|
| |\| | | | | |
|
| | | |_|/ /
| |/| | | |
|
| |\| | | |
| |/ / /
|/| | | |
|
| | |/ /
| | |
| | |
| | | |
follow up to #140412
|
| |\| | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
mosquitto needs a lot of attention concerning its config because it doesn't
parse it very well, often ignoring trailing parts of lines, duplicated config
keys, or just looking back way further in the file to associated config keys
with previously defined items than might be expected.
this replaces the mosquitto module completely. we now have a hierarchical config
that flattens out to the mosquitto format (hopefully) without introducing spooky
action at a distance.
|
| |\| |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
pkgs/development/python-modules/jupyter-client/default.nix
pkgs/development/python-modules/jupyterlab-git/default.nix
|
| | | | |
|
| |\| | |
|
| | | | |
|
| |\| | |
|
| | | | |
|