You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The mls team feature now has a lock status. If the current installation has default settings defined in wire-server's `values.yaml`, the `lockStatus` has to be added, e.g.:
2
+
3
+
```yaml
4
+
mls:
5
+
defaults:
6
+
status: enabled
7
+
config:
8
+
protocolToggleUsers: []
9
+
defaultProtocol: mls
10
+
allowedCipherSuites: [1]
11
+
defaultCipherSuite: 1
12
+
supportedProtocols: [proteus, mls] # must contain defaultProtocol
Copy file name to clipboardExpand all lines: docs/src/developer/reference/config-options.md
+13-12Lines changed: 13 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -299,17 +299,18 @@ If this feature is disabled then clients will use the Proteus protocol with this
299
299
300
300
The default configuration that applies to all teams that didn't explicitly change their feature configuration can be given in galley's `featureFlags` section in the config file:
301
301
302
-
```
302
+
```yaml
303
303
# galley.yaml
304
304
mls:
305
305
defaults:
306
-
status: disabled
306
+
status: enabled
307
307
config:
308
308
protocolToggleUsers: []
309
-
defaultProtocol: proteus
309
+
defaultProtocol: mls
310
310
allowedCipherSuites: [1]
311
311
defaultCipherSuite: 1
312
-
312
+
supportedProtocols: [proteus, mls] # must contain defaultProtocol
313
+
lockStatus: locked
313
314
```
314
315
315
316
This default configuration can be overriden on a per-team basis through the [feature config API](../developer/features.md)
@@ -748,7 +749,7 @@ to the configuration example above:
748
749
749
750

750
751
751
-
<!--
752
+
<!--
752
753
Unfortunately, kroki currently doesn't work on our CI: SQPIT-1810
The webapp runs its own web server (a NodeJS server) to serve static files and the webapp config (based on environment variables).
772
-
In a multi-ingress configuration, a single webapp instance will be deployed and be accessible from multiple domains (say `webapp.red.example.com` and `webapp.green.example.com`).
773
-
When the webapp is loaded from one of those domains it first does a request to the web server to get the config (that will give it, for example, the backend endpoint that it should hit).
772
+
The webapp runs its own web server (a NodeJS server) to serve static files and the webapp config (based on environment variables).
773
+
In a multi-ingress configuration, a single webapp instance will be deployed and be accessible from multiple domains (say `webapp.red.example.com` and `webapp.green.example.com`).
774
+
When the webapp is loaded from one of those domains it first does a request to the web server to get the config (that will give it, for example, the backend endpoint that it should hit).
774
775
775
-
Because of the single instance nature of the webapp, by default the configuration is static and the root url to the backend API can be set there (say `nginz-https.root.example.com`).
776
+
Because of the single instance nature of the webapp, by default the configuration is static and the root url to the backend API can be set there (say `nginz-https.root.example.com`).
776
777
In order to completely hide this root domain to the webapp, an environment variable can be set to allow the webapp hostname to be used to generate the API endpoint, team settings links, account page links and CSP headers.
777
778
778
-
The "hostname" is the result of the domain name minus the `webapp.` part of it.
779
+
The "hostname" is the result of the domain name minus the `webapp.` part of it.
779
780
So querying the webapp on `webapp.red.example.com` will resolve to `red.example.com`.
780
781
781
782
To enable dynamic hostname replacement, first set this variable:
@@ -784,7 +785,7 @@ To enable dynamic hostname replacement, first set this variable:
784
785
ENABLE_DYNAMIC_HOSTNAME="true"
785
786
```
786
787
787
-
Then, any other variable that will contain the string `[[hostname]]` will be replaced by the hostname of the running webapp. (eg. if a webapp is running on `webapp.red.example.com` then any occurrence of `[[hostname]]` in the config will be replaced by `red.example.com`).
788
+
Then, any other variable that will contain the string `[[hostname]]` will be replaced by the hostname of the running webapp. (eg. if a webapp is running on `webapp.red.example.com` then any occurrence of `[[hostname]]` in the config will be replaced by `red.example.com`).
788
789
789
790
You may use the template variable `[[hostname]]` in any environment variable to not provide (reveal) actual domain names.
0 commit comments