+3
nixos/doc/manual/redirects.json
+3
nixos/doc/manual/redirects.json
···
+15
nixos/doc/manual/release-notes/rl-2511.section.md
+15
nixos/doc/manual/release-notes/rl-2511.section.md
···- `services.gitea` supports sending notifications with sendmail again. To do this, activate the parameter `services.gitea.mailerUseSendmail` and configure SMTP server.- `systemd.extraConfig` and `boot.initrd.systemd.extraConfig` was converted to RFC42-style `systemd.settings.Manager` and `boot.initrd.systemd.settings.Manager` respectively.
···- `services.gitea` supports sending notifications with sendmail again. To do this, activate the parameter `services.gitea.mailerUseSendmail` and configure SMTP server.+- Revamp of the ACME certificate acquisication and renewal process to help scale systems with lots (100+) of certificates.+Units and targets have been reshaped to better support more specific dependency propagation and avoid+If a service requires a syntactically valid certificate to start it should now depend on the `acme-{certname}.service` unit.+We now always generate initial self-signed certificates as this drastically simplifies the dependency structure. As a result, the option `security.acme.preliminarySelfsigned` has been removed.+Instead of the previous `acme-finished-{certname}.target`s there are now `acme-order-renew-{certname}.service`s that will be activated+in a delayed fashion to ensure that bootstrapping with servers like nginx that take part in the acquisition/renewal process works+Note that system activation will complete before all certificates may have been renewed or acquired.- `systemd.extraConfig` and `boot.initrd.systemd.extraConfig` was converted to RFC42-style `systemd.settings.Manager` and `boot.initrd.systemd.settings.Manager` respectively.
+8
nixos/modules/security/acme/default.md
+8
nixos/modules/security/acme/default.md
···+## Ensuring dependencies for services that need to be reloaded when a certificate challenges {#module-security-acme-reload-dependencies}+Services that depend on ACME certificates and need to be reloaded can use one of two approaches to reload upon successfull certificate acquisition or renewal:+1. **Using the `security.acme.certs.<name>.reloadServices` option**: This will cause `systemctl try-reload-or-restart` to be run for the listed services.+2. **Using a separate reload unit**: if you need perform more complex actions you can implement a separate reload unit but need to ensure that it lists the `acme-renew-<name>.service` unit both as `wantedBy` AND `after`. See the nginx module implementation with its `nginx-config-reload` service.