nixos/release-notes: use redis as example for extras in synapse
postgres isn't such a good idea actually because it's added by default to the wrapper.
This commit is contained in:
parent
701d0e1da6
commit
9f6ed8c2b2
1 changed files with 1 additions and 1 deletions
|
@ -53,7 +53,7 @@
|
|||
- The `matrix-synapse` package & module have undergone some significant internal changes, for most setups no intervention is needed, though:
|
||||
- The option [`services.matrix-synapse.package`](#opt-services.matrix-synapse.package) is now read-only. For modifying the package, use an overlay which modifies `matrix-synapse-unwrapped` instead. More on that below.
|
||||
- The `enableSystemd` & `enableRedis` arguments have been removed and `matrix-synapse` has been renamed to `matrix-synapse-unwrapped`. Also, several optional dependencies (such as `psycopg2` or `authlib`) have been removed.
|
||||
- These optional dependencies are automatically added via a wrapper (`pkgs.matrix-synapse.override { extras = ["postgres"]; }` for `psycopg2` for instance) if the relevant config section is declared in `services.matrix-synapse.settings`. For instance, if [`services.matrix-synapse.settings.database.name`](#opt-services.matrix-synapse.settings.database.name) is `psycopg2`, `"postgres"` will be automatically added to the `extras` list of `pkgs.matrix-synapse`.
|
||||
- These optional dependencies are automatically added via a wrapper (`pkgs.matrix-synapse.override { extras = ["redis"]; }` for `hiredis` & `txredisapi` for instance) if the relevant config section is declared in `services.matrix-synapse.settings`. For instance, if `services.matrix-synapse.settings.redis.enabled` is set to `true`, `"redis"` will be automatically added to the `extras` list of `pkgs.matrix-synapse`.
|
||||
- A list of all extras (and the extras enabled by default) can be found at the [option's reference for `services.matrix-synapse.extras`](#opt-services.matrix-synapse.extras).
|
||||
- In some cases (e.g. for running synapse workers) it was necessary to re-use the `PYTHONPATH` of `matrix-synapse.service`'s environment to have all plugins available. This isn't necessary anymore, instead `config.services.matrix-synapse.package` can be used as it points to the wrapper with properly configured `extras` and also all plugins defined via [`services.matrix-synapse.plugins`](#opt-services.matrix-synapse.plugins) available. This is also the reason for why the option is read-only now, it's supposed to be set by the module only.
|
||||
|
||||
|
|
Loading…
Reference in a new issue