Matrix/element-web-Github
1
0
Fork 0
mirror of https://github.com/vector-im/element-web.git synced 2024-11-22 16:18:14 +08:00
Code Issues Packages Projects Releases Wiki Activity
349c9b0c26
element-web-Github/config.sample.json

52 lines
1.6 KiB
JSON
Raw Normal View History

Add config file for default hs/is urls
2015-10-02 18:48:52 +08: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 08:59:28 +08: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-24 03:16:00 +08: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 08:59:28 +08: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 07:47:03 +08:00
"disable_custom_urls": false,
"disable_guests": false,
"disable_login_language_selector": false,
"disable_3pid_login": false,
Add doc for 'force_verification config option As per https://github.com/element-hq/matrix-react-sdk/pull/29
2024-09-11 23:01:13 +08:00
"force_verification": false,
Fix sample config brand
2020-07-15 18:26:26 +08:00
"brand": "Element",
Use the default integrations URLs in the sample localhost is not a sensible default
2016-10-15 01:21:26 +08: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 15:03:50 +08: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 default_widget_container_height in sample config The key name was just wrong
2024-09-11 17:14:40 +08:00
"default_widget_container_height": 280,
Update SdkConfig usage to use new translation layer + update config.md docs (#21429) * Update SdkConfig usage to use new translation layer * Appease the linter * WIP refactor of config documentation * Finish re-writing config.md * Update surrounding documentation * Apply suggestions from code review Co-authored-by: Germain <germains@element.io> * Textual updates Co-authored-by: Germain <germains@element.io>
2022-03-19 00:12:44 +08:00
"default_country_code": "GB",
"show_labs_settings": false,
Apply prettier formatting
2022-12-09 20:28:29 +08:00
"features": {},
Added default_federate property
2017-05-08 18:25:45 +08:00
"default_federate": true,
support concept of default theme
2017-10-21 01:41:39 +08:00
"default_theme": "light",
Update SdkConfig usage to use new translation layer + update config.md docs (#21429) * Update SdkConfig usage to use new translation layer * Appease the linter * WIP refactor of config documentation * Finish re-writing config.md * Update surrounding documentation * Apply suggestions from code review Co-authored-by: Germain <germains@element.io> * Textual updates Co-authored-by: Germain <germains@element.io>
2022-03-19 00:12:44 +08:00
"room_directory": {
Apply prettier formatting
2022-12-09 20:28:29 +08:00
"servers": ["matrix.org"]
Add welcomeUserId to sample config
2017-05-12 23:12:17 +08:00
},
Add dosable-presence-by-hs option to sample config
2018-03-20 00:49:41 +08:00
"enable_presence_by_hs_url": {
Update sample config Signed-off-by: Aaron Raimist <aaron@raim.ist>
2019-11-30 10:17:15 +08:00
"https://matrix.org": false,
"https://matrix-client.matrix.org": false
add settingDefaults to sample config
2019-05-31 20:52:29 +08:00
},
Update SdkConfig usage to use new translation layer + update config.md docs (#21429) * Update SdkConfig usage to use new translation layer * Appease the linter * WIP refactor of config documentation * Finish re-writing config.md * Update surrounding documentation * Apply suggestions from code review Co-authored-by: Germain <germains@element.io> * Textual updates Co-authored-by: Germain <germains@element.io>
2022-03-19 00:12:44 +08:00
"setting_defaults": {
add example default setting
2019-10-07 20:46:50 +08:00
"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-19 05:47:56 +08:00
},
"jitsi": {
Update SdkConfig usage to use new translation layer + update config.md docs (#21429) * Update SdkConfig usage to use new translation layer * Appease the linter * WIP refactor of config documentation * Finish re-writing config.md * Update surrounding documentation * Apply suggestions from code review Co-authored-by: Germain <germains@element.io> * Textual updates Co-authored-by: Germain <germains@element.io>
2022-03-19 00:12:44 +08:00
"preferred_domain": "meet.element.io"
Provide sample config for the map_style_url (#21078)
2022-02-15 02:14:04 +08:00
},
Element Call video rooms (#23246) * Add an element_call_url config option * Document feature_element_call_video_rooms
2022-09-16 23:13:05 +08:00
"element_call": {
Add Element Call `brand` (#23443)
2022-10-08 01:32:12 +08:00
"url": "https://call.element.io",
Add Element Call participant limit (#23431)
2022-10-08 04:00:38 +08:00
"participant_limit": 8,
Add Element Call `brand` (#23443)
2022-10-08 01:32:12 +08:00
"brand": "Element Call"
Element Call video rooms (#23246) * Add an element_call_url config option * Document feature_element_call_video_rooms
2022-09-16 23:13:05 +08:00
},
Provide sample config for the map_style_url (#21078)
2022-02-15 02:14:04 +08:00
"map_style_url": "https://api.maptiler.com/maps/streets/style.json?key=fU3vlMsMn4Jb6dnEIFsx"
Add config file for default hs/is urls
2015-10-02 18:48:52 +08:00
}
Reference in New Issue Copy Permalink