| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
| |
I changed my nickname from Ninjatrappeur to Picnoir. My github id is
stable, it shouldn't break too much stuff.
I took advantage of this handle change to remove myself from the
hostapd maintainers: I don't use NixOS as a router anymore.
|
| | |
|
| |
|
|
|
|
| |
The only breaking change here is that Yarn drops support for NodeJS versions <18.12
Besides that, no major changes that I think deserve a mention
|
| |\
| |
| | |
home-assistant: custom components and lovelace modules
|
| | | |
|
| | |
| |
| |
| |
| | |
Make sure we properly remove custom components and custom lovelace
modules, when they're not configured anymore.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Allows passing custom component packages, that get installed into
home-assistant's state directory.
Python depedencies, that are propagated from the custom component
get passed into `extraPackages`, so they are available to
home-assistant at runtime.
This is implemented in a way, that allows coexistence with custom
components not managed through the NixOS module.
|
| | |
| |
| |
| |
| | |
Allows the installation of custom lovelace modules, that can inject
css/js into the frontend and offer a wide variety of widgets.
|
| |\ \
| | |
| | | |
nixos/gnome/at-spi2-core: fix disabling a11y in all contexts
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
`environment.variables` gets sourced by shells & the x11 wrapper
through bash's `/etc/profile`, but not by systemd services, dbus
services, wayland sessions...
`environment.sessionVariables` sets these variables with PAM early in
the login process so it gets applied in all contexts.
I ran into a similar issue before in #109060.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The setting
QEMU_NET_OPTS="hostfwd=tcp::2222-:22"
caused the VM's port 2222 to be advertised on the host as
`0.0.0.0:2222`, thus anybody in the local network of the host
could SSH into the VM.
Instead, port-forward to localhost only.
Use `127.0.0.1` also on the VM side, otherwise connections to
services that, in the VM, bind to `127.0.0.1` only
(doing the safe approach) do not work.
See e.g. https://github.com/NixOS/nixpkgs/issues/100192
for more info why localhost listening is the best default.
|
| |\ \ \ |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | | |
nixos/restic: allow timer to be disabled
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
nixos/installer: remove nixos-option compat shim
|
| | | |_|_|/
| |/| | |
| | | | |
| | | | | |
It's been two years.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
The default was accidentally changed to false in #262790
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
systemd-lib: cleanup empty lines in unit files
|
| | | | | | | |
|
| | |/ / / /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
While the word 'simply' is usually added to encourage readers, it often has the
opposite effect and may even appear condescending, especially when the reader
runs into trouble trying to apply the suggestions from the documentation. It is
almost always an improvement to simply drop the word from the sentence.
(there are more possible improvements like this, we can apply those in separate
PRs)
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
nixos/sudo: bring in line with release notes
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
This makes things more uniform; moreover, users can now inject rules before this.
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
This makes the generated sudoers a touch easier to read.
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
nix: 2.17.1 -> 2.18.1
|
| | | | | | | | |
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
azure-agent: add dependencies for its extensions
|
| | |/ / / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
waagent's extension `Microsoft.OSTCExtensions.VMAccessForLinux` requires Python, otherwise it would be failed to install with the following error message in `/var/log/waagent.log`:
```
No Python interpreter found on the box
```
waagent's extension `Microsoft.CPlat.Core.RunCommandLinux` needs lsof, otherwise it would produce the following error message in `/var/log/waagent.log`:
```
/var/lib/waagent/Microsoft.Azure.Extensions.CustomScript-2.1.10/bin/custom-script-shim: line 60: lsof: command not found
```
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
nixos/boot: add postResumeCommands option
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Adds a postResumeCommands option to the initramfs to allow inserting
code to execute after the device has attempted to resume, and before
filesystems are mounted. This allows to inject code for operations like
wiping the rootfs on boot; if those were instead put in
postDeviceCommands, on a hibernated device, they would execute before
the device resumes from hibernation.
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| |\ \ \ \ \ \ \ \
| |_|/ / / / / /
|/| | | | | | | |
trust-dns: 0.23.0 -> 0.24.0
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
upstream is in the process of renaming to `hickory-dns`.
a consequence of this is that the main binary has been renamed from
`trust-dns` to `hickory-dns` and the repository has been moved (though
for the time being the old repo is still usable on account that it
redirects to the new one).
see: <https://bluejekyll.github.io/blog/posts/announcing-hickory-dns/>
|
| | | | | | | | |
| | | | | | | |
| | | | | | | | |
This change enables CUDA support by allowing access to /dev/nvidia0.
|
| |\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
netdata: 1.43.0 -> 1.43.2 and add systemd-journal plugin
|