| Commit message (Collapse) | Author | Age |
|---|
| |\
| |
| | |
Traefik: 1.7.14 -> 2.2.0
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This commit:
1. Updates the path of the traefik package, so that the out output is
used.
2. Adapts the configuration settings and options to Traefik v2.
3. Formats the NixOS traefik service using nixfmt.
|
| |\ \
| | |
| | | |
nodejs: use python3 if possible
|
| | | | |
|
| |\ \ \
| |_|/
|/| | |
prometheus: use runCommandNoCCLocal for config gen
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
nixos/doc: Document breaking change to Haskell dev shells
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | | |
nixos/nftables: fix typo in ruleset example
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
specialisation: replace nesting with named configurations
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Co-authored-by: worldofpeace <worldofpeace@protonmail.ch>
|
| | |_|_|/ /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
According to my analysis the last critical fix went into v5.4.23, I have
confirmed this by running WebGL over night and haven't seen a single
i915 GPU hang. Lets remove the notes from the release notes.
(cherry picked from commit da764d22ce3b698707861d58824843ded87cbb0a)
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We already set the relevant env vars in the systemd services. That does
not help one when executing any of the executables outside a service,
e.g. when creating a new user.
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
roundcube: use pspell for spellchecking
|
| | | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | | |
By default, upstream enables a third party service in the cloud:
https://github.com/roundcube/roundcubemail/blob/1.4.3/config/defaults.inc.php#L790-L798
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Fixes https://github.com/NixOS/nixpkgs/issues/82777
(cherry picked from commit 7c9f30befaa5360a9c3d7d566fdf1922f84ee6c5)
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Fixes #79180.
(cherry picked from commit ec11fd21637535d87cdbac95c8caa095a73674ef)
|
| | | | | |
| | | | |
| | | | |
| | | | | |
As discovered by flokli.
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
nextcloud: Review installation upgrade warning wording
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The new wording does not assume the user is upgrading.
This is because a user could be setting up a new installation on 20.03
on a server that has a 19.09 or before stateVersion!!
The new wording ensures that confusion is reduced by stating that they
do not have to care about the assumed 16→17 transition.
Then, the wording explains that they should, and how to upgrade to
version 18.
It also reviews the confusing wording about "multiple" upgrades.
* * *
The only thing we cannot really do is stop a fresh install of 17 if
there was no previous install, as it cannot be detected. That makes a
useless upgrade forced for new users with old state versions.
It is also important to state that they must set their package to
Nextcloud 18, as future upgrades to Nextcloud will not allow an uprade
from 17!
I assume future warning messages will exist specifically stating what to
do to go from 18 to 19, then 19 to 20, etc...
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
nixos/ssh: don't accept ssh-dss keys
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
These have been deprecated long enough. I think this default was even
made non-functional by 2337c7522af3b186d4d7ecefe9e19c33aafc6626. But
it's still a scary thing to see there.
Fixes https://github.com/NixOS/nixpkgs/issues/33381.
|
| | |_|_|/ / /
|/| | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
we use stdenv.hostPlatform.uname.processor, which I believe is just like
`uname -p`.
Example values:
```
(import <nixpkgs> { system = "x86_64-linux"; }).stdenv.hostPlatform.uname.processor
"x86_64"
(import <nixpkgs> { system = "aarch64-linux"; }).stdenv.hostPlatform.uname.processor
aarch64
(import <nixpkgs> { system = "armv7l-linux"; }).stdenv.hostPlatform.uname.processor
"armv7l"
```
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
This reverts commit 21b50e6f6879f22b9261362bfd6dce26b7611e18.
|
| | | | | | | |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
iso-image: normalize volumeID
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The volumeID will now be in the format of:
nixos-$EDITON-$RELEASE-$ARCH
an example for the minimal image would look like:
nixos-minimal-20.09-x86-64-linux
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This is per the advice of the osinfo-db maintainers https://gitlab.com/libosinfo/osinfo-db/-/merge_requests/107#note_313094852
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This allows to have multiple certificates with the same common name.
Lego uses in its internal directory the common name to name the certificate.
fixes #84409
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
nixos: default nix.maxJobs to auto
|
| | | |_|_|/ / /
| |/| | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Instead of making the configuration less portable by hard coding the number of
jobs equal to the cores we can also let nix set the same number at runtime.
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
bridges by default
This is an backward incompatible change from upstream dhcpcd [0], as
this could have easily locked me out of my box.
As dhcpcd doesn't allow to use only a blacklist (denyinterfaces in
dhcpcd.conf) of devices and use all remaining devices, while explicitly
allowing some interfaces like bridges, I think the best option would be
to not change anything about it and just educate the users here about
that edge case and how to solve it.
[0] https://roy.marples.name/archives/dhcpcd-discuss/0002621.html
(cherry picked from commit eeeb2bf8035b309a636d596de6a3b1d52ca427b1)
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
I've had Netdata crash on me sometimes. Rarely but more than once. And I lost days of data before I noticed.
Let's be nice and restart it on failures by default.
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
hydra: 2020-03-24 -> 2020-04-07
|
| | | |_|/ / / /
| |/| | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Also removed `pkgs.hydra-flakes` since flake-support has been merged
into master[1]. Because of that, `pkgs.hydra-unstable` is now compiled
against `pkgs.nixFlakes` and currently requires a patch since Hydra's
master doesn't compile[2] atm.
[1] https://github.com/NixOS/hydra/pull/730
[2] https://github.com/NixOS/hydra/pull/732
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Cc: @flokli
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
malcontent: 0.6.0 → 0.7.0
|
| | | | | | | | | |
|
| | | |_|_|/ / /
| |/| | | | |
| | | | | | |
| | | | | | | |
The 0.7.0 update allows us to split the package.
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
treewide: use runtimeShell in nixos/
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This is needed for cross-compilation.
|
| | | | | | | | | |
|