+3
nixos/doc/manual/release-notes/rl-2411.section.md
+3
nixos/doc/manual/release-notes/rl-2411.section.md
···- The nvidia driver no longer defaults to the proprietary driver starting with version 560. You will need to manually set `hardware.nvidia.open` to select the proprietary or open driver.- `singularity-tools` have the `storeDir` argument removed from its override interface and use `builtins.storeDir` instead.
···+- The `mautrix-signal` module was adapted to incorporate the configuration rearrangement that resulted from the update to the mautrix bridgev2 architecture. Pre-0.7.0 configurations should continue to work.- The nvidia driver no longer defaults to the proprietary driver starting with version 560. You will need to manually set `hardware.nvidia.open` to select the proprietary or open driver.- `singularity-tools` have the `storeDir` argument removed from its override interface and use `builtins.storeDir` instead.
+32
nixos/modules/services/matrix/mautrix-signal.md
+32
nixos/modules/services/matrix/mautrix-signal.md
···
···+## Migrating from an older configuration {#module-services-mautrix-signal-migrate-configuration}
+59
-37
nixos/modules/services/matrix/mautrix-signal.nix
+59
-37
nixos/modules/services/matrix/mautrix-signal.nix
···············-| if env.MAUTRIX_SIGNAL_BRIDGE_LOGIN_SHARED_SECRET then .bridge.login_shared_secret_map.[.homeserver.domain] = env.MAUTRIX_SIGNAL_BRIDGE_LOGIN_SHARED_SECRET else . end' \···
······+# By default, the following keys/secrets are set to `generate`. This would break when the service···+Get an example configuration by executing `mautrix-signal -c example.yaml --generate-example-config`······+| if env.MAUTRIX_SIGNAL_BRIDGE_LOGIN_SHARED_SECRET then .double_puppet.secrets.[.homeserver.domain] = env.MAUTRIX_SIGNAL_BRIDGE_LOGIN_SHARED_SECRET else . end' \···