mirror of
https://github.com/SchildiChat/element-web.git
synced 2024-10-01 01:26:12 -04:00
e1eb16ce46
Effectively fixes https://github.com/vector-im/riot-web/issues/11074 Effectively fixes https://github.com/vector-im/riot-web/issues/7112 Fixes https://github.com/vector-im/riot-web/issues/6930 Fixes Jitsi widgets not working for guests (https://github.com/vector-im/riot-web/issues/8933) Fixes https://github.com/vector-im/riot-web/issues/5048 Previously we were relying on an integration manager to be defined, functional, and alive in order to join Jitsi calls. This commit changes this so we aren't reliant on an integration manager for Jitsi calls at all, and gives people the option of choosing a Jitsi server via the config.json. This side is just the wrapper/shell: the logic is mostly in the react-sdk (to be linked via PRs). This layer simply has an HTML file exported that can be used to render a Jitsi widget, and the react-sdk constructs a URL to access it locally. This is similar to how the mobile apps handle Jitsi widgets: instead of iframing the widget URL directly into the app, they pull apart the widget information and natively render it. We're effectively doing the same here by parsing the widget options and using our local wrapper instead of whatever happens to be defined in the widget state event. Integration managers should still continue to offer a widget URL for Jitsi widgets as this is what the spec requires. A large part of this is based upon Dimension's handling of Jitsi and widgets in general: a license has been granted to allow Riot (and therefore the react-sdk) to use the code and be inspired by it.
150 lines
9.0 KiB
Markdown
150 lines
9.0 KiB
Markdown
Configuration
|
|
=============
|
|
|
|
You can configure the app by copying `config.sample.json` to
|
|
`config.json` and customising it:
|
|
|
|
For a good example, see https://riot.im/develop/config.json.
|
|
|
|
1. `default_server_config` sets the default homeserver and identity server URL for
|
|
Riot to use. The object is the same as returned by [https://<server_name>/.well-known/matrix/client](https://matrix.org/docs/spec/client_server/latest.html#get-well-known-matrix-client),
|
|
with added support for a `server_name` under the `m.homeserver` section to display
|
|
a custom homeserver name. Alternatively, the config can contain a `default_server_name`
|
|
instead which is where Riot will go to get that same object, although this option is
|
|
deprecated - see the `.well-known` link above for more information on using this option.
|
|
Note that the `default_server_name` is used to get a complete server configuration
|
|
whereas the `server_name` in the `default_server_config` is for display purposes only.
|
|
* *Note*: The URLs can also be individually specified as `default_hs_url` and
|
|
`default_is_url`, however these are deprecated. They are maintained for backwards
|
|
compatibility with older configurations. `default_is_url` is respected only
|
|
if `default_hs_url` is used.
|
|
* Riot will fail to load if a mix of `default_server_config`, `default_server_name`, or
|
|
`default_hs_url` is specified. When multiple sources are specified, it is unclear
|
|
which should take priority and therefore the application cannot continue.
|
|
* As of Riot 1.4.0, identity servers are optional. See [Identity servers](#identity-servers) below.
|
|
1. `features`: Lookup of optional features that may be `enable`d, `disable`d, or
|
|
exposed to the user in the `labs` section of settings. The available
|
|
optional experimental features vary from release to release and are [documented](labs.md). The feature flag process is
|
|
[documented](feature-flags.md) as well.
|
|
1. `showLabsSettings`: Shows the "labs" tab of user settings even when no `features` are enabled
|
|
or present. Useful for getting at settings which may be otherwise hidden.
|
|
1. `brand`: String to pass to your homeserver when configuring email notifications, to let the
|
|
homeserver know what email template to use when talking to you.
|
|
1. `branding`: Configures various branding and logo details, such as:
|
|
1. `welcomeBackgroundUrl`: An image to use as a wallpaper outside the app
|
|
during authentication flows
|
|
1. `authHeaderLogoUrl`: An logo image that is shown in the header during
|
|
authentication flows
|
|
1. `authFooterLinks`: a list of links to show in the authentication page footer:
|
|
`[{"text": "Link text", "url": "https://link.target"}, {"text": "Other link", ...}]`
|
|
1. `reportEvent`: Configures the dialog for reporting content to the homeserver
|
|
admin.
|
|
1. `adminMessageMD`: An extra message to show on the reporting dialog to
|
|
mention homeserver-specific policies. Accepts Markdown.
|
|
1. `integrations_ui_url`: URL to the web interface for the integrations server. The integrations
|
|
server is not Riot and normally not your homeserver either. The integration server settings
|
|
may be left blank to disable integrations.
|
|
1. `integrations_rest_url`: URL to the REST interface for the integrations server.
|
|
1. `integrations_widgets_urls`: list of URLs to the REST interface for the widget integrations server.
|
|
1. `bug_report_endpoint_url`: endpoint to send bug reports to (must be running a
|
|
https://github.com/matrix-org/rageshake server). Bug reports are sent when a user clicks
|
|
"Send Logs" within the application. Bug reports can be disabled by leaving the
|
|
`bug_report_endpoint_url` out of your config file.
|
|
1. `roomDirectory`: config for the public room directory. This section is optional.
|
|
1. `roomDirectory.servers`: List of other homeservers' directories to include in the drop
|
|
down list. Optional.
|
|
1. `default_theme`: name of theme to use by default (e.g. 'light')
|
|
1. `update_base_url` (electron app only): HTTPS URL to a web server to download
|
|
updates from. This should be the path to the directory containing `macos`
|
|
and `win32` (for update packages, not installer packages).
|
|
1. `piwik`: Analytics can be disabled by setting `piwik: false` or by leaving the piwik config
|
|
option out of your config file. If you want to enable analytics, set `piwik` to be an object
|
|
containing the following properties:
|
|
1. `url`: The URL of the Piwik instance to use for collecting analytics
|
|
1. `whitelistedHSUrls`: a list of HS URLs to not redact from the analytics
|
|
1. `whitelistedISUrls`: a list of IS URLs to not redact from the analytics
|
|
1. `siteId`: The Piwik Site ID to use when sending analytics to the Piwik server configured above
|
|
1. `welcomeUserId`: the user ID of a bot to invite whenever users register that can give them a tour
|
|
1. `embeddedPages`: Configures the pages displayed in portions of Riot that
|
|
embed static files, such as:
|
|
1. `welcomeUrl`: Initial content shown on the outside of the app when not
|
|
logged in. Defaults to `welcome.html` supplied with Riot.
|
|
1. `homeUrl`: Content shown on the inside of the app when a specific room is
|
|
not selected. By default, no home page is configured. If one is set, a
|
|
button to access it will be shown in the top left menu.
|
|
1. `defaultCountryCode`: The ISO 3166 alpha2 country code to use when showing
|
|
country selectors, like the phone number input on the registration page.
|
|
Defaults to `GB` if the given code is unknown or not provided.
|
|
1. `settingDefaults`: Defaults for settings that support the `config` level,
|
|
as an object mapping setting name to value (note that the "theme" setting
|
|
is special cased to the `default_theme` in the config file).
|
|
1. `disable_custom_urls`: disallow the user to change the
|
|
default homeserver when signing up or logging in.
|
|
1. `permalinkPrefix`: Used to change the URL that Riot generates permalinks with.
|
|
By default, this is "https://matrix.to" to generate matrix.to (spec) permalinks.
|
|
Set this to your Riot instance URL if you run an unfederated server (eg:
|
|
"https://riot.example.org").
|
|
1. `jitsi`: Used to change the default conference options.
|
|
1. `preferredDomain`: The domain name of the preferred Jitsi instance. Defaults
|
|
to `jitsi.riot.im`. This is used whenever a user clicks on the voice/video
|
|
call buttons - integration managers may use a different domain.
|
|
1. `externalApiUrl`: The URL to the Jitsi Meet API script. This is required
|
|
for showing any Jitsi widgets, no matter the source. Defaults to
|
|
`https://jitsi.riot.im/libs/external_api.min.js`.
|
|
|
|
Note that `index.html` also has an og:image meta tag that is set to an image
|
|
hosted on riot.im. This is the image used if links to your copy of Riot
|
|
appear in some websites like Facebook, and indeed Riot itself. This has to be
|
|
static in the HTML and an absolute URL (and HTTP rather than HTTPS), so it's
|
|
not possible for this to be an option in config.json. If you'd like to change
|
|
it, you can build Riot, but run
|
|
`RIOT_OG_IMAGE_URL="http://example.com/logo.png" yarn build`.
|
|
Alternatively, you can edit the `og:image` meta tag in `index.html` directly
|
|
each time you download a new version of Riot.
|
|
|
|
Identity servers
|
|
================
|
|
|
|
The identity server is used for inviting other users to a room via third party
|
|
identifiers like emails and phone numbers. It is not used to store your password
|
|
or account information.
|
|
|
|
As of Riot 1.4.0, all identity server functions are optional and you are
|
|
prompted to agree to terms before data is sent to the identity server.
|
|
|
|
Riot will check multiple sources when looking for an identity server to use in
|
|
the following order of preference:
|
|
|
|
1. The identity server set in the user's account data
|
|
* For a new user, no value is present in their account data. It is only set
|
|
if the user visits Settings and manually changes their identity server.
|
|
2. The identity server provided by the `.well-known` lookup that occurred at
|
|
login
|
|
3. The identity server provided by the Riot config file
|
|
|
|
If none of these sources have an identity server set, then Riot will prompt the
|
|
user to set an identity server first when attempting to use features that
|
|
require one.
|
|
|
|
Currently the only two public identity servers are https://vector.im and
|
|
https://matrix.org, however in the future identity servers will be
|
|
decentralised.
|
|
|
|
Desktop app configuration
|
|
=========================
|
|
|
|
To run multiple instances of the desktop app for different accounts, you can
|
|
launch the executable with the `--profile` argument followed by a unique
|
|
identifier, e.g `riot-web --profile Work` for it to run a separate profile and
|
|
not interfere with the default one.
|
|
|
|
Alternatively, a custom location for the profile data can be specified using the
|
|
`--profile-dir` flag followed by the desired path.
|
|
|
|
+ `%APPDATA%\$NAME\config.json` on Windows
|
|
+ `$XDG_CONFIG_HOME\$NAME\config.json` or `~/.config/$NAME/config.json` on Linux
|
|
+ `~Library/Application Support/$NAME/config.json` on macOS
|
|
|
|
In the paths above, `$NAME` is typically `Riot`, unless you use `--profile
|
|
$PROFILE` in which case it becomes `Riot-$PROFILE`.
|