OpenCloud
/
element-web
mirror of https://github.com/vector-im/element-web
1
0
Fork 0
Code Issues Releases Wiki Activity
element-web/config.sample.json

60 lines
1.9 KiB
JSON
Raw Normal View History

Add config file for default hs/is urls
2015-10-02 12:48:52 +02:00
{
Validate default homeserver config before loading the app Implements the process described here: https://github.com/vector-im/riot-web/issues/9290#issuecomment-481966910 The expectation is that later layers (like the react-sdk) will make use of the `validated_discovery_config` option instead of interpreting the config themselves. We intentionally block the UI from loading here to avoid races between discovery and the app loading.
2019-04-16 02:59:28 +02:00
"default_server_config": {
"m.homeserver": {
Update sample config for new matrix.org CS API URL This was missed in https://github.com/vector-im/riot-web/pull/11112
2019-10-23 21:16:00 +02:00
"base_url": "https://matrix-client.matrix.org",
Validate default homeserver config before loading the app Implements the process described here: https://github.com/vector-im/riot-web/issues/9290#issuecomment-481966910 The expectation is that later layers (like the react-sdk) will make use of the `validated_discovery_config` option instead of interpreting the config themselves. We intentionally block the UI from loading here to avoid races between discovery and the app loading.
2019-04-16 02:59:28 +02:00
"server_name": "matrix.org"
},
"m.identity_server": {
"base_url": "https://vector.im"
}
},
replace some of the status.im theme with general config options
2017-11-12 00:47:03 +01:00
"disable_custom_urls": false,
"disable_guests": false,
"disable_login_language_selector": false,
"disable_3pid_login": false,
Change default brand to Riot & update sample config
2016-10-04 11:23:38 +02:00
"brand": "Riot",
Use the default integrations URLs in the sample localhost is not a sensible default
2016-10-14 19:21:26 +02:00
"integrations_ui_url": "https://scalar.vector.im/",
"integrations_rest_url": "https://scalar.vector.im/api",
Provide our common integrations_widget_urls defaults for sample config Closes #10454
2019-08-26 09:03:50 +02:00
"integrations_widgets_urls": [
"https://scalar.vector.im/_matrix/integrations/v1",
"https://scalar.vector.im/api",
"https://scalar-staging.vector.im/_matrix/integrations/v1",
"https://scalar-staging.vector.im/api",
"https://scalar-staging.riot.im/scalar/api"
],
Fix bug report endpoint in config.sample.json. Not sure why this was like this - has vector.im/bugs *ever* worked?
2017-05-09 13:27:41 +02:00
"bug_report_endpoint_url": "https://riot.im/bugreports/submit",
Add docs for defaultCountryCode
2019-06-01 05:23:58 +02:00
"defaultCountryCode": "GB",
Add 'showLabsSettings' flag to docs+sample config
2019-05-31 04:03:42 +02:00
"showLabsSettings": false,
add features example to config.sample.json
2017-10-20 14:41:55 +02:00
"features": {
Update references to features
2019-07-25 22:53:53 +02:00
"feature_pinning": "labs",
"feature_custom_status": "labs",
"feature_custom_tags": "labs",
"feature_state_counters": "labs"
add features example to config.sample.json
2017-10-20 14:41:55 +02:00
},
Added default_federate property
2017-05-08 12:25:45 +02:00
"default_federate": true,
support concept of default theme
2017-10-20 19:41:39 +02:00
"default_theme": "light",
Add roomDirectory to sample config
2016-09-15 19:42:00 +02:00
"roomDirectory": {
Update sample config
2016-09-28 11:13:35 +02:00
"servers": [
"matrix.org"
Remove the client side filtering from the room dir This removes the ability for the client to filter remote room directories by network, since the /thirdparty/protocols API does not yet work for remote servers. They would only get the main list now though anyway, so there is no point in us continuing to support it.
2016-12-16 15:17:13 +01:00
]
Add welcomeUserId to sample config
2017-05-12 17:12:17 +02:00
},
Merge branch 'develop' into new-guest-access
2017-05-30 22:06:45 +02:00
"welcomeUserId": "@riot-bot:matrix.org",
sample piwik config Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
2017-05-28 12:27:33 +02:00
"piwik": {
explicit protocol in configs, otherwise breaks in Electron when it tries file:// Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
2017-05-29 20:32:44 +02:00
"url": "https://piwik.riot.im/",
move piwik whitelists to conf and add piwik config.json info to readme Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
2017-11-19 16:36:28 +01:00
"whitelistedHSUrls": ["https://matrix.org"],
"whitelistedISUrls": ["https://vector.im", "https://matrix.org"],
sample piwik config Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
2017-05-28 12:27:33 +02:00
"siteId": 1
Add dosable-presence-by-hs option to sample config
2018-03-19 17:49:41 +01:00
},
"enable_presence_by_hs_url": {
Update sample config Signed-off-by: Aaron Raimist <aaron@raim.ist>
2019-11-30 03:17:15 +01:00
"https://matrix.org": false,
"https://matrix-client.matrix.org": false
add settingDefaults to sample config
2019-05-31 14:52:29 +02:00
},
add example default setting
2019-10-07 14:46:50 +02:00
"settingDefaults": {
"breadcrumbs": true
Use a local widget wrapper for Jitsi calls 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.
2020-03-18 22:47:56 +01:00
},
"jitsi": {
"preferredDomain": "jitsi.riot.im",
"externalApiUrl": "https://jitsi.riot.im/libs/external_api.min.js"
Add roomDirectory to sample config
2016-09-15 19:42:00 +02:00
}
Add config file for default hs/is urls
2015-10-02 12:48:52 +02:00
}