"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "docs/reference/config-options.md" between
wire-server-2021-09-14.tar.gz and wire-server-2021-10-01.tar.gz

About: Wire (server) offers end-to-end encrypted messaging, file-sharing, video and voice calls, and guest rooms for external communication (back-end server).

config-options.md  (wire-server-2021-09-14):config-options.md  (wire-server-2021-10-01)
# Config Options {#RefConfigOptions} # Config Options {#RefConfigOptions}
Fragment. Fragment.
This page is about the yaml files that determine the configuration of This page is about the yaml files that determine the configuration of
the Wire backend services. the Wire backend services.
## Settings ## Settings in galley
``` ```
# [galley.yaml] # [galley.yaml]
settings: settings:
enableIndexedBillingTeamMembers: false enableIndexedBillingTeamMembers: false
``` ```
### Indexed Billing Team Members ### Indexed Billing Team Members
Use indexed billing team members for journaling. When `enabled`, Use indexed billing team members for journaling. When `enabled`,
skipping to change at line 144 skipping to change at line 144
Example value for the config section: Example value for the config section:
```yaml ```yaml
conferenceCalling: conferenceCalling:
defaults: defaults:
status: enabled status: enabled
``` ```
The `conferenceCalling` section is optional in `featureFlags`. If it is omitted then it is assumed to be `enabled`. The `conferenceCalling` section is optional in `featureFlags`. If it is omitted then it is assumed to be `enabled`.
See also: conference falling for personal accounts (below).
### File Sharing ### File Sharing
File sharing is enabled by default. If you want to disable it for all teams, ad d this to your feature config settings: File sharing is enabled by default. If you want to disable it for all teams, ad d this to your feature config settings:
``` ```
fileSharing: fileSharing:
defaults: defaults:
status: enabled status: enabled
``` ```
skipping to change at line 272 skipping to change at line 274
```yaml ```yaml
federator: federator:
optSettings: optSettings:
federationStrategy: federationStrategy:
allowedDomains: allowedDomains:
- server2.example.com - server2.example.com
useSystemCAStore: false useSystemCAStore: false
clientCertificate: client.pem clientCertificate: client.pem
clientPrivateKey: client-key.pem clientPrivateKey: client-key.pem
``` ```
## Settings in brig
Some features (as of the time of writing this: only
`conferenceCalling`) allow to set defaults for personal accounts in
brig. Those are taken into account in galley's end-points `GET
/feature-configs*`.
To be specific:
### Conference Calling
Two values can be configured for personal accounts: a default for when
the user record contains `null` as feature config, and default that
should be inserted into the user record when creating new users:
```
# [brig.yaml]
settings:
setFeatureFlags:
conferenceCalling:
defaultForNew:
status: disabled
defaultForNull:
status: enabled
```
You can omit the entire `conferenceCalling` block, but not parts of
it. Built-in defaults: `defaultForNew: null` (user record attribute
is left empty); `defaultForNull: enabled`. This maintains behavior
prior to the introduction of this change, while allowing site owners
to postpone the decision about the default setting.
When new users are created, their config will be initialized with
what's in `defaultForNew`.
When a `null` value is encountered, it is assumed to be
`defaultForNull`.
(Introduced in https://github.com/wireapp/wire-server/pull/1811.)
 End of changes. 3 change blocks. 
1 lines changed or deleted 3 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)