From f7a3b7ed7f4078d5022fdc4e6183c35975536a21 Mon Sep 17 00:00:00 2001 From: H-Shay Date: Wed, 1 Dec 2021 18:12:48 +0000 Subject: [PATCH] deploy: 84dc50e160a2ec6590813374b5a1e58b97f7a18d --- develop/404.html | 2 +- develop/CAPTCHA_SETUP.html | 2 +- develop/MSC1711_certificates_FAQ.html | 2 +- develop/admin_api/account_validity.html | 2 +- develop/admin_api/delete_group.html | 2 +- develop/admin_api/event_reports.html | 2 +- develop/admin_api/media_admin_api.html | 2 +- develop/admin_api/purge_history_api.html | 2 +- develop/admin_api/register_api.html | 2 +- develop/admin_api/room_membership.html | 2 +- develop/admin_api/rooms.html | 2 +- develop/admin_api/server_notices.html | 2 +- develop/admin_api/statistics.html | 2 +- develop/admin_api/user_admin_api.html | 2 +- develop/admin_api/version_api.html | 2 +- develop/application_services.html | 2 +- develop/auth_chain_difference_algorithm.html | 2 +- develop/code_style.html | 2 +- develop/consent_tracking.html | 2 +- develop/delegate.html | 2 +- develop/deprecation_policy.html | 10 +- develop/development/cas.html | 2 +- develop/development/contributing_guide.html | 6 +- develop/development/database_schema.html | 2 +- .../development/experimental_features.html | 2 +- develop/development/git.html | 2 +- .../internal_documentation/index.html | 2 +- develop/development/room-dag-concepts.html | 2 +- develop/development/saml.html | 2 +- develop/development/url_previews.html | 2 +- develop/federate.html | 2 +- develop/index.html | 2 +- develop/jwt.html | 2 +- develop/log_contexts.html | 2 +- develop/manhole.html | 2 +- develop/media_repository.html | 2 +- develop/message_retention_policies.html | 2 +- develop/metrics-howto.html | 6 +- .../modules/account_validity_callbacks.html | 2 +- ...ackground_update_controller_callbacks.html | 2 +- develop/modules/index.html | 2 +- .../password_auth_provider_callbacks.html | 2 +- develop/modules/porting_legacy_module.html | 2 +- .../modules/presence_router_callbacks.html | 2 +- develop/modules/spam_checker_callbacks.html | 2 +- .../modules/third_party_rules_callbacks.html | 2 +- develop/modules/writing_a_module.html | 2 +- develop/openid.html | 2 +- develop/opentracing.html | 2 +- ...ing_synapse_on_single_board_computers.html | 302 ++++++++++++++ develop/password_auth_providers.html | 2 +- develop/postgres.html | 2 +- develop/print.html | 327 ++++++++++++++- develop/replication.html | 2 +- develop/reverse_proxy.html | 2 +- develop/room_and_user_statistics.html | 2 +- develop/searchindex.js | 2 +- develop/searchindex.json | 2 +- develop/server_notices.html | 2 +- develop/setup/forward_proxy.html | 2 +- develop/setup/installation.html | 2 +- develop/sso_mapping_providers.html | 2 +- develop/structured_logging.html | 2 +- develop/synctl_workers.html | 2 +- develop/systemd-with-workers/index.html | 2 +- develop/tcp_replication.html | 2 +- develop/templates.html | 2 +- develop/turn-howto.html | 2 +- develop/upgrade.html | 2 +- .../admin_api/background_updates.html | 2 +- .../usage/administration/admin_api/index.html | 2 +- .../admin_api/registration_tokens.html | 2 +- develop/usage/administration/admin_faq.html | 315 ++++++++++++++ .../database_maintenance_tools.html | 279 +++++++++++++ develop/usage/administration/index.html | 2 +- develop/usage/administration/request_log.html | 10 +- .../usage/administration/state_groups.html | 268 ++++++++++++ ...anding_synapse_through_grafana_graphs.html | 294 +++++++++++++ .../administration/useful_sql_for_admins.html | 389 ++++++++++++++++++ .../homeserver_sample_config.html | 2 +- develop/usage/configuration/index.html | 2 +- .../configuration/logging_sample_config.html | 2 +- .../user_authentication/index.html | 2 +- .../single_sign_on/cas.html | 2 +- .../single_sign_on/index.html | 2 +- .../single_sign_on/saml.html | 2 +- develop/user_directory.html | 2 +- develop/welcome_and_overview.html | 2 +- develop/workers.html | 2 +- 89 files changed, 2271 insertions(+), 91 deletions(-) create mode 100644 develop/other/running_synapse_on_single_board_computers.html create mode 100644 develop/usage/administration/admin_faq.html create mode 100644 develop/usage/administration/database_maintenance_tools.html create mode 100644 develop/usage/administration/state_groups.html create mode 100644 develop/usage/administration/understanding_synapse_through_grafana_graphs.html create mode 100644 develop/usage/administration/useful_sql_for_admins.html diff --git a/develop/404.html b/develop/404.html index 96417bb629..d628504b99 100644 --- a/develop/404.html +++ b/develop/404.html @@ -101,7 +101,7 @@ - IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringRequest log formatScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation Policy + IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringUnderstanding Synapse Through Grafana GraphsUseful SQL for AdminsDatabase Maintenance ToolsState GroupsRequest log formatAdmin FAQScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation PolicyRunning Synapse on a Single-Board Computer diff --git a/develop/CAPTCHA_SETUP.html b/develop/CAPTCHA_SETUP.html index b07a365d74..5831ab620b 100644 --- a/develop/CAPTCHA_SETUP.html +++ b/develop/CAPTCHA_SETUP.html @@ -99,7 +99,7 @@ - IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringRequest log formatScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation Policy + IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringUnderstanding Synapse Through Grafana GraphsUseful SQL for AdminsDatabase Maintenance ToolsState GroupsRequest log formatAdmin FAQScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation PolicyRunning Synapse on a Single-Board Computer diff --git a/develop/MSC1711_certificates_FAQ.html b/develop/MSC1711_certificates_FAQ.html index dfb4ecbd9e..4eece7aaef 100644 --- a/develop/MSC1711_certificates_FAQ.html +++ b/develop/MSC1711_certificates_FAQ.html @@ -99,7 +99,7 @@ - IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringRequest log formatScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation Policy + IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringUnderstanding Synapse Through Grafana GraphsUseful SQL for AdminsDatabase Maintenance ToolsState GroupsRequest log formatAdmin FAQScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation PolicyRunning Synapse on a Single-Board Computer diff --git a/develop/admin_api/account_validity.html b/develop/admin_api/account_validity.html index 0c1b5ffd29..bb8480e630 100644 --- a/develop/admin_api/account_validity.html +++ b/develop/admin_api/account_validity.html @@ -99,7 +99,7 @@ - IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringRequest log formatScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation Policy + IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringUnderstanding Synapse Through Grafana GraphsUseful SQL for AdminsDatabase Maintenance ToolsState GroupsRequest log formatAdmin FAQScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation PolicyRunning Synapse on a Single-Board Computer diff --git a/develop/admin_api/delete_group.html b/develop/admin_api/delete_group.html index d2f899f0ff..6fc69b3293 100644 --- a/develop/admin_api/delete_group.html +++ b/develop/admin_api/delete_group.html @@ -99,7 +99,7 @@ - IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringRequest log formatScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation Policy + IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringUnderstanding Synapse Through Grafana GraphsUseful SQL for AdminsDatabase Maintenance ToolsState GroupsRequest log formatAdmin FAQScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation PolicyRunning Synapse on a Single-Board Computer diff --git a/develop/admin_api/event_reports.html b/develop/admin_api/event_reports.html index 81cac5e48f..cd497e87a2 100644 --- a/develop/admin_api/event_reports.html +++ b/develop/admin_api/event_reports.html @@ -99,7 +99,7 @@ - IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringRequest log formatScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation Policy + IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringUnderstanding Synapse Through Grafana GraphsUseful SQL for AdminsDatabase Maintenance ToolsState GroupsRequest log formatAdmin FAQScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation PolicyRunning Synapse on a Single-Board Computer diff --git a/develop/admin_api/media_admin_api.html b/develop/admin_api/media_admin_api.html index a4ae2d566c..ebb752b594 100644 --- a/develop/admin_api/media_admin_api.html +++ b/develop/admin_api/media_admin_api.html @@ -99,7 +99,7 @@ - IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringRequest log formatScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation Policy + IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringUnderstanding Synapse Through Grafana GraphsUseful SQL for AdminsDatabase Maintenance ToolsState GroupsRequest log formatAdmin FAQScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation PolicyRunning Synapse on a Single-Board Computer diff --git a/develop/admin_api/purge_history_api.html b/develop/admin_api/purge_history_api.html index 724b3e7e6c..34ac1ee94f 100644 --- a/develop/admin_api/purge_history_api.html +++ b/develop/admin_api/purge_history_api.html @@ -99,7 +99,7 @@ - IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringRequest log formatScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation Policy + IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringUnderstanding Synapse Through Grafana GraphsUseful SQL for AdminsDatabase Maintenance ToolsState GroupsRequest log formatAdmin FAQScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation PolicyRunning Synapse on a Single-Board Computer diff --git a/develop/admin_api/register_api.html b/develop/admin_api/register_api.html index ccb475a9fd..4498af61b7 100644 --- a/develop/admin_api/register_api.html +++ b/develop/admin_api/register_api.html @@ -99,7 +99,7 @@ - IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringRequest log formatScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation Policy + IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringUnderstanding Synapse Through Grafana GraphsUseful SQL for AdminsDatabase Maintenance ToolsState GroupsRequest log formatAdmin FAQScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation PolicyRunning Synapse on a Single-Board Computer diff --git a/develop/admin_api/room_membership.html b/develop/admin_api/room_membership.html index 5ba707bef2..f288e972e5 100644 --- a/develop/admin_api/room_membership.html +++ b/develop/admin_api/room_membership.html @@ -99,7 +99,7 @@ - IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringRequest log formatScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation Policy + IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringUnderstanding Synapse Through Grafana GraphsUseful SQL for AdminsDatabase Maintenance ToolsState GroupsRequest log formatAdmin FAQScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation PolicyRunning Synapse on a Single-Board Computer diff --git a/develop/admin_api/rooms.html b/develop/admin_api/rooms.html index 6f7d8a15d8..bd6304a3e2 100644 --- a/develop/admin_api/rooms.html +++ b/develop/admin_api/rooms.html @@ -99,7 +99,7 @@ - IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringRequest log formatScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation Policy + IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringUnderstanding Synapse Through Grafana GraphsUseful SQL for AdminsDatabase Maintenance ToolsState GroupsRequest log formatAdmin FAQScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation PolicyRunning Synapse on a Single-Board Computer diff --git a/develop/admin_api/server_notices.html b/develop/admin_api/server_notices.html index f49f11de10..a2242d3867 100644 --- a/develop/admin_api/server_notices.html +++ b/develop/admin_api/server_notices.html @@ -99,7 +99,7 @@ - IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringRequest log formatScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation Policy + IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringUnderstanding Synapse Through Grafana GraphsUseful SQL for AdminsDatabase Maintenance ToolsState GroupsRequest log formatAdmin FAQScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation PolicyRunning Synapse on a Single-Board Computer diff --git a/develop/admin_api/statistics.html b/develop/admin_api/statistics.html index fbb18220fa..a6bb8d4a95 100644 --- a/develop/admin_api/statistics.html +++ b/develop/admin_api/statistics.html @@ -99,7 +99,7 @@ - IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringRequest log formatScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation Policy + IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringUnderstanding Synapse Through Grafana GraphsUseful SQL for AdminsDatabase Maintenance ToolsState GroupsRequest log formatAdmin FAQScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation PolicyRunning Synapse on a Single-Board Computer diff --git a/develop/admin_api/user_admin_api.html b/develop/admin_api/user_admin_api.html index d92d7b6998..9c62c25719 100644 --- a/develop/admin_api/user_admin_api.html +++ b/develop/admin_api/user_admin_api.html @@ -99,7 +99,7 @@ - IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringRequest log formatScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation Policy + IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringUnderstanding Synapse Through Grafana GraphsUseful SQL for AdminsDatabase Maintenance ToolsState GroupsRequest log formatAdmin FAQScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation PolicyRunning Synapse on a Single-Board Computer diff --git a/develop/admin_api/version_api.html b/develop/admin_api/version_api.html index 052de18fbc..5725cc960a 100644 --- a/develop/admin_api/version_api.html +++ b/develop/admin_api/version_api.html @@ -99,7 +99,7 @@ - IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringRequest log formatScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation Policy + IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringUnderstanding Synapse Through Grafana GraphsUseful SQL for AdminsDatabase Maintenance ToolsState GroupsRequest log formatAdmin FAQScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation PolicyRunning Synapse on a Single-Board Computer diff --git a/develop/application_services.html b/develop/application_services.html index 2c64e8f716..b4cd396113 100644 --- a/develop/application_services.html +++ b/develop/application_services.html @@ -99,7 +99,7 @@ - IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringRequest log formatScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation Policy + IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringUnderstanding Synapse Through Grafana GraphsUseful SQL for AdminsDatabase Maintenance ToolsState GroupsRequest log formatAdmin FAQScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation PolicyRunning Synapse on a Single-Board Computer diff --git a/develop/auth_chain_difference_algorithm.html b/develop/auth_chain_difference_algorithm.html index dbff0bad94..04a6e98b4c 100644 --- a/develop/auth_chain_difference_algorithm.html +++ b/develop/auth_chain_difference_algorithm.html @@ -99,7 +99,7 @@ - IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringRequest log formatScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation Policy + IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringUnderstanding Synapse Through Grafana GraphsUseful SQL for AdminsDatabase Maintenance ToolsState GroupsRequest log formatAdmin FAQScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation PolicyRunning Synapse on a Single-Board Computer diff --git a/develop/code_style.html b/develop/code_style.html index 8e66d7ab75..947fff3a63 100644 --- a/develop/code_style.html +++ b/develop/code_style.html @@ -99,7 +99,7 @@ - IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringRequest log formatScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation Policy + IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringUnderstanding Synapse Through Grafana GraphsUseful SQL for AdminsDatabase Maintenance ToolsState GroupsRequest log formatAdmin FAQScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation PolicyRunning Synapse on a Single-Board Computer diff --git a/develop/consent_tracking.html b/develop/consent_tracking.html index fe9306b7ae..7030972709 100644 --- a/develop/consent_tracking.html +++ b/develop/consent_tracking.html @@ -99,7 +99,7 @@ - IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringRequest log formatScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation Policy + IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringUnderstanding Synapse Through Grafana GraphsUseful SQL for AdminsDatabase Maintenance ToolsState GroupsRequest log formatAdmin FAQScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation PolicyRunning Synapse on a Single-Board Computer diff --git a/develop/delegate.html b/develop/delegate.html index 18952abaff..d7c46ecb00 100644 --- a/develop/delegate.html +++ b/develop/delegate.html @@ -99,7 +99,7 @@ - IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringRequest log formatScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation Policy + IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringUnderstanding Synapse Through Grafana GraphsUseful SQL for AdminsDatabase Maintenance ToolsState GroupsRequest log formatAdmin FAQScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation PolicyRunning Synapse on a Single-Board Computer diff --git a/develop/deprecation_policy.html b/develop/deprecation_policy.html index c9a6226f9d..7ef4f6ee96 100644 --- a/develop/deprecation_policy.html +++ b/develop/deprecation_policy.html @@ -99,7 +99,7 @@ - IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringRequest log formatScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation Policy + IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringUnderstanding Synapse Through Grafana GraphsUseful SQL for AdminsDatabase Maintenance ToolsState GroupsRequest log formatAdmin FAQScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation PolicyRunning Synapse on a Single-Board Computer @@ -215,6 +215,10 @@ to constantly update their platform dependencies to the latest versions.
I've been running my homeserver on a cubietruck at home now for some time and am often replying to statements like "you need loads of ram to join large rooms" with "it works fine for me". I thought it might be useful to curate a summary of the issues you're likely to run into to help as a scaling-down guide, maybe highlight these for development work or end up as documentation. It seems that once you get up to about 4x1.5GHz arm64 4GiB these issues are no longer a problem.
This is the main reason people have a poor matrix experience on resource constrained homeservers. Element web will frequently be saying the server is offline while the python process will be pegged at 100% cpu. This feature is used to tell when other users are active (have a client app in the foreground) and therefore more likely to respond, but requires a lot of network activity to maintain even when nobody is talking in a room.
While synapse does have some performance issues with presence #3971, the fundamental problem is that this is an easy feature to implement for a centralised service at nearly no overhead, but federation makes it combinatorial #8055. There is also a client-side config option which disables the UI and idle tracking enable_presence_by_hs_url to blacklist the largest instances but I didn't notice much difference, so I recommend disabling the feature entirely at the server level as well.
Joining a "large", federated room will initially fail with the below message in Element web, but waiting a while (10-60mins) and trying again will succeed without any issue. What counts as "large" is not message history, user count, connections to homeservers or even a simple count of the state events, it is instead how long the state resolution algorithm takes. However, each of those numbers are reasonable proxies, so we can use them as estimates since user count is one of the few things you see before joining.
This is #1211 and will also hopefully be mitigated by peeking matrix-org/matrix-doc#2753 so at least you don't need to wait for a join to complete before finding out if it's the kind of room you want. Note that you should first disable presence, otherwise it'll just make the situation worse #3120. There is a lot of database interaction too, so make sure you've migrated your data from the default sqlite to postgresql. Personally, I recommend patience - once the initial join is complete there's rarely any issues with actually interacting with the room, but if you like you can just block "large" rooms entirely.
Anything that requires modifying the device list #7721 will take a while to propagate, again taking the client "Offline" until it's complete. This includes signing in and out, editing the public name and verifying e2ee. The main mitigation I recommend is to keep long-running sessions open e.g. by using Firefox SSB "Use this site in App mode" or Chromium PWA "Install Element".
Put the below in a new file at /etc/matrix-synapse/conf.d/sbc.yaml to override the defaults in homeserver.yaml.
# Set to false to disable presence tracking on this homeserver. +use_presence: false + +# When this is enabled, the room "complexity" will be checked before a user +# joins a new remote room. If it is above the complexity limit, the server will +# disallow joining, or will instantly leave. +limit_remote_rooms: + # Uncomment to enable room complexity checking. + #enabled: true + complexity: 3.0 + +# Database configuration +database: + name: psycopg2 + args: + user: matrix-synapse + # Generate a long, secure one with a password manager + password: hunter2 + database: matrix-synapse + host: localhost + cp_min: 5 + cp_max: 10 +
Currently the complexity is measured by current_state_events / 500. You can find join times and your most complex rooms like this:
admin@homeserver:~$ zgrep '/client/r0/join/' /var/log/matrix-synapse/homeserver.log* | awk '{print $18, $25}' | sort --human-numeric-sort +29.922sec/-0.002sec /_matrix/client/r0/join/%23debian-fasttrack%3Apoddery.com +182.088sec/0.003sec /_matrix/client/r0/join/%23decentralizedweb-general%3Amatrix.org +911.625sec/-570.847sec /_matrix/client/r0/join/%23synapse%3Amatrix.org + +admin@homeserver:~$ sudo --user postgres psql matrix-synapse --command 'select canonical_alias, joined_members, current_state_events from room_stats_state natural join room_stats_current where canonical_alias is not null order by current_state_events desc fetch first 5 rows only' + canonical_alias | joined_members | current_state_events +-------------------------------+----------------+---------------------- + #_oftc_#debian:matrix.org | 871 | 52355 + #matrix:matrix.org | 6379 | 10684 + #irc:matrix.org | 461 | 3751 + #decentralizedweb-general:matrix.org | 997 | 1509 + #whatsapp:maunium.net | 554 | 854 +
It is possible monitor much of the internal state of Synapse using Prometheus metrics and Grafana. A guide for configuring Synapse to provide metrics is available here and information on setting up Grafana is here. In this setup, Prometheus will periodically scrape the information Synapse provides and store a record of it over time. Grafana is then used as an interface to query and present this information through a series of pretty graphs.
Once you have grafana set up, and assuming you're using our grafana dashboard template, look for the following graphs when debugging a slow/overloaded Synapse:
This, along with the CPU and Memory graphs, is a good way to check the general health of your Synapse instance. It represents how long it takes for a user on your homeserver to send a message.
These graphs show the database transactions that are occurring the most frequently, as well as those are that are taking the most amount of time to execute.
In the first graph, we can see obvious spikes corresponding to lots of get_user_by_id transactions. This would be useful information to figure out which part of the Synapse codebase is potentially creating a heavy load on the system. However, be sure to cross-reference this with Transaction Duration, which states that get_users_by_id is actually a very quick database transaction and isn't causing as much load as others, like persist_events:
get_user_by_id
get_users_by_id
persist_events
Still, it's probably worth investigating why we're getting users from the database that often, and whether it's possible to reduce the amount of queries we make by adjusting our cache factor(s).
The persist_events transaction is responsible for saving new room events to the Synapse database, so can often show a high transaction duration.
The charts in the "Federation" section show information about incoming and outgoing federation requests. Federation data can be divided into two basic types:
The "Outgoing EDUs by type" chart shows the EDUs within outgoing federation requests by type: m.device_list_update, m.direct_to_device, m.presence, m.receipt, m.typing.
m.device_list_update
m.direct_to_device
m.presence
m.receipt
m.typing
If you see a large number of m.presence EDUs and are having trouble with too much CPU load, you can disable presence in the Synapse config. See also #3971.
presence
This is quite a useful graph. It shows how many times Synapse attempts to retrieve a piece of data from a cache which the cache did not contain, thus resulting in a call to the database. We can see here that the _get_joined_profile_from_event_id cache is being requested a lot, and often the data we're after is not cached.
_get_joined_profile_from_event_id
Cross-referencing this with the Eviction Rate graph, which shows that entries are being evicted from _get_joined_profile_from_event_id quite often:
we should probably consider raising the size of that cache by raising its cache factor (a multiplier value for the size of an individual cache). Information on doing so is available here (note that the configuration of individual cache factors through the configuration file is available in Synapse v1.14.0+, whereas doing so through environment variables has been supported for a very long time). Note that this will increase Synapse's overall memory usage.
Forward extremities are the leaf events at the end of a DAG in a room, aka events that have no children. The more exist in a room, the more state resolution that Synapse needs to perform (hint: it's an expensive operation). While Synapse has code to prevent too many of these existing at one time in a room, bugs can sometimes make them crop up again.
If a room has >10 forward extremities, it's worth checking which room is the culprit and potentially removing them using the SQL queries mentioned in #1760.
Large spikes in garbage collection times (bigger than shown here, I'm talking in the multiple seconds range), can cause lots of problems in Synapse performance. It's more an indicator of problems, and a symptom of other problems though, so check other graphs for what might be causing it.
If you're still having performance problems with your Synapse instance and you've tried everything you can, it may just be a lack of system resources. Consider adding more CPU and RAM, and make use of worker mode to make use of multiple CPU cores / multiple machines for your homeserver.
SELECT pg_size_pretty( pg_database_size( 'matrix' ) );
pg_size_pretty +---------------- + 6420 MB +(1 row) +
SELECT r.name, s.room_id, s.current_state_events + FROM room_stats_current s + LEFT JOIN room_stats_state r USING (room_id) + ORDER BY current_state_events DESC + LIMIT 20; +
and by state_group_events count:
SELECT rss.name, s.room_id, count(s.room_id) FROM state_groups_state s +LEFT JOIN room_stats_state rss USING (room_id) +GROUP BY s.room_id, rss.name +ORDER BY count(s.room_id) DESC +LIMIT 20; +
plus same, but with join removed for performance reasons:
SELECT s.room_id, count(s.room_id) FROM state_groups_state s +GROUP BY s.room_id +ORDER BY count(s.room_id) DESC +LIMIT 20; +
SELECT relname, n_live_tup as rows + FROM pg_stat_user_tables + ORDER BY n_live_tup DESC + LIMIT 20; +
This query is quick, but may be very approximate, for exact number of rows use SELECT COUNT(*) FROM <table_name>.
SELECT COUNT(*) FROM <table_name>
state_groups_state - 161687170 +event_auth - 8584785 +event_edges - 6995633 +event_json - 6585916 +event_reference_hashes - 6580990 +events - 6578879 +received_transactions - 5713989 +event_to_state_groups - 4873377 +stream_ordering_to_exterm - 4136285 +current_state_delta_stream - 3770972 +event_search - 3670521 +state_events - 2845082 +room_memberships - 2785854 +cache_invalidation_stream - 2448218 +state_groups - 1255467 +state_group_edges - 1229849 +current_state_events - 1222905 +users_in_public_rooms - 364059 +device_lists_stream - 326903 +user_directory_search - 316433 +
SELECT e.room_id, r.name, COUNT(e.event_id) cnt FROM events e +LEFT JOIN room_stats_state r USING (room_id) +WHERE e.origin_server_ts >= DATE_PART('epoch', NOW() - INTERVAL '1 day') * 1000 GROUP BY e.room_id, r.name ORDER BY cnt DESC LIMIT 20; +
SELECT user_id, SUM(total_events) + FROM user_stats_historical + WHERE TO_TIMESTAMP(end_ts/1000) AT TIME ZONE 'UTC' > date_trunc('day', now() - interval '1 month') + GROUP BY user_id + ORDER BY SUM(total_events) DESC + LIMIT 20; +
SELECT e.room_id, r.name, e.event_id, e.type, e.content, j.json FROM events e + LEFT JOIN event_json j USING (room_id) + LEFT JOIN room_stats_state r USING (room_id) + WHERE sender = '@LOGIN:example.com' + AND e.type = 'm.room.message' + ORDER BY stream_ordering DESC + LIMIT 100; +
SELECT nspname || '.' || relname AS "relation", + pg_size_pretty(pg_total_relation_size(C.oid)) AS "total_size" + FROM pg_class C + LEFT JOIN pg_namespace N ON (N.oid = C.relnamespace) + WHERE nspname NOT IN ('pg_catalog', 'information_schema') + AND C.relkind <> 'i' + AND nspname !~ '^pg_toast' + ORDER BY pg_total_relation_size(C.oid) DESC + LIMIT 20; +
public.state_groups_state - 27 GB +public.event_json - 9855 MB +public.events - 3675 MB +public.event_edges - 3404 MB +public.received_transactions - 2745 MB +public.event_reference_hashes - 1864 MB +public.event_auth - 1775 MB +public.stream_ordering_to_exterm - 1663 MB +public.event_search - 1370 MB +public.room_memberships - 1050 MB +public.event_to_state_groups - 948 MB +public.current_state_delta_stream - 711 MB +public.state_events - 611 MB +public.presence_stream - 530 MB +public.current_state_events - 525 MB +public.cache_invalidation_stream - 466 MB +public.receipts_linearized - 279 MB +public.state_groups - 160 MB +public.device_lists_remote_cache - 124 MB +public.state_group_edges - 122 MB +
echo "select event_json.room_id,room_stats_state.name from event_json,room_stats_state where room_stats_state.room_id=event_json.room_id" | psql synapse | sort | uniq -c | sort -n
9459 !FPUfgzXYWTKgIrwKxW:matrix.org | This Week in Matrix + 9459 !FPUfgzXYWTKgIrwKxW:matrix.org | This Week in Matrix (TWIM) + 17799 !iDIOImbmXxwNngznsa:matrix.org | Linux in Russian + 18739 !GnEEPYXUhoaHbkFBNX:matrix.org | Riot Android + 23373 !QtykxKocfZaZOUrTwp:matrix.org | Matrix HQ + 39504 !gTQfWzbYncrtNrvEkB:matrix.org | ru.[matrix] + 43601 !iNmaIQExDMeqdITdHH:matrix.org | Riot + 43601 !iNmaIQExDMeqdITdHH:matrix.org | Riot Web/Desktop +
SELECT rss.room_id, rss.name, rss.canonical_alias, rss.topic, rss.encryption, rsc.joined_members, rsc.local_users_in_room, rss.join_rules +FROM room_stats_state rss +LEFT JOIN room_stats_current rsc USING (room_id) +WHERE room_id IN (WHERE room_id IN ( + '!OGEhHVWSdvArJzumhm:matrix.org', + '!YTvKGNlinIzlkMTVRl:matrix.org' +) +
This blog post by Victor Berger explains how to use many of the tools listed on this page: https://levans.fr/shrink-synapse-database.html
The purge remote media API allows server admins to purge old cached remote media.
There is no purge API for local media because you may be the only one with a copy. If you are sure you want to delete local media you could use something like the following to delete media that hasn't been accessed in a while.
find /path/to/synapse/media_store/local_content -atime +365 -delete +find /path/to/synapse/media_store/local_thumbnails -atime +365 -delete +
This will delete media that hasn't been accessed in 365 days.
Warning, check noatime flag: You also have to double-check that the filesystem where synapse's media store don't have noatime flag. Check it with mount, noatime is something that is usually enabled by default to reduce read-write operations in the filesystem for a feature is not so demanded.
mount
noatime
The purge history API allows server admins to purge historic events from their database, reclaiming disk space.
Cleans a synapse Postgres database of deleted messages and abandoned rooms.
Tool for compressing (deduplicating) state_groups_state table.
state_groups_state
Some easy SQL that reports useful stat about Matrix Synapse database.
As a general rule, I encourage people who want to understand the deepest darkest secrets of the database schema to drop by #synapse-dev:matrix.org and ask questions.
However, one question that comes up frequently is that of how "state groups" work, and why the state_groups_state table gets so big, so here's an attempt to answer that question.
We need to be able to relatively quickly calculate the state of a room at any point in that room's history. In other words, we need to know the state of the room at each event in that room. This is done as follows:
A sequence of events where the state is the same are grouped together into a state_group; the mapping is recorded in event_to_state_groups. (Technically speaking, since a state event usually changes the state in the room, we are recording the state of the room after the given event id: which is to say, to a handwavey simplification, the first event in a state group is normally a state event, and others in the same state group are normally non-state-events.)
state_group
event_to_state_groups
state_groups records, for each state group, the id of the room that we're looking at, and also the id of the first event in that group. (I'm not sure if that event id is used much in practice.)
state_groups
Now, if we stored all the room state for each state_group, that would be a huge amount of data. Instead, for each state group, we normally store the difference between the state in that group and some other state group, and only occasionally (every 100 state changes or so) record the full state.
So, most state groups have an entry in state_group_edges (don't ask me why it's not a column in state_groups) which records the previous state group in the room, and state_groups_state records the differences in state since that previous state group.
state_group_edges
A full state group just records the event id for each piece of state in the room at that point.
There are various reasons that we can end up creating many more state groups than we need: see https://github.com/matrix-org/synapse/issues/3364 for more details.
There is a tool at https://github.com/matrix-org/rust-synapse-compress-state which can compress the state_groups_state on a room by-room basis (essentially, it reduces the number of "full" state groups). This can result in dramatic reductions of the storage used.
HTTP request logs are written by synapse (see site.py for details).
site.py
See the following for how to decode the dense data available from the default logging configuration.
KKKK
LLLL
MMMM
NNNN
OOOO
If your server already has an admin account you should use the user admin API to promote other accounts to become admins. See User Admin API
If you don't have any admin accounts yet you won't be able to use the admin API so you'll have to edit the database manually. Manually editing the database is generally not recommended so once you have an admin account, use the admin APIs to make further changes.
UPDATE users SET admin = 1 WHERE name = '@foo:bar.com'; +
Run this sql query on your db:
SELECT * FROM destinations; +
SELECT DISTINCT split_part(state_key, ':', 2) + FROM current_state_events AS c + INNER JOIN room_memberships AS m USING (room_id, event_id) + WHERE room_id = '!cURbafjkfsMDVwdRDQ:matrix.org' AND membership = 'join'; +
SELECT NAME from users; +
See https://github.com/matrix-org/synapse/blob/master/README.rst#password-reset
Deleting your database is unlikely to make anything better.
It's easy to make the mistake of thinking that you can start again from a clean slate by dropping your database, but things don't work like that in a federated network: lots of other servers have information about your server.
For example: other servers might think that you are in a room, your server will think that you are not, and you'll probably be unable to interact with that room in a sensible way ever again.
In general, there are better solutions to any problem than dropping the database. Come and seek help in https://matrix.to/#/#synapse:matrix.org.
There are two exceptions when it might be sensible to delete your database and start again:
server_name
Using the following curl command:
curl -H 'Authorization: Bearer <access-token>' -X DELETE https://matrix.org/_matrix/client/r0/directory/room/<room-alias> +
<access-token> - can be obtained in riot by looking in the riot settings, down the bottom is: +Access Token:<click to reveal>
<room-alias> - the room alias, eg. #my_room:matrix.org this possibly needs to be URL encoded also, for example %23my_room%3Amatrix.org
Synapse tags each log line according to the HTTP request it is processing. When it finishes processing each request, it logs a line containing the words Processed request: . For example:
Processed request:
2019-02-14 22:35:08,196 - synapse.access.http.8008 - 302 - INFO - GET-37 - ::1 - 8008 - {@richvdh:localhost} Processed request: 0.173sec/0.001sec (0.002sec, 0.000sec) (0.027sec/0.026sec/2) 687B 200 "GET /_matrix/client/r0/sync HTTP/1.1" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36" [0 dbevts]" +
Here we can see that the request has been tagged with GET-37. (The tag depends on the method of the HTTP request, so might start with GET-, PUT-, POST-, OPTIONS- or DELETE-.) So to find all lines corresponding to this request, we can do:
GET-37
GET-
PUT-
POST-
OPTIONS-
DELETE-
grep 'GET-37' homeserver.log +
If you want to paste that output into a github issue or matrix room, please remember to surround it with triple-backticks (```) to make it legible (see https://help.github.com/en/articles/basic-writing-and-formatting-syntax#quoting-code).
See Request log format.
SELECT s.canonical_alias, g.room_id, count(*) AS num_rows +FROM + state_groups_state AS g, + room_stats_state AS s +WHERE g.room_id = s.room_id +GROUP BY s.canonical_alias, g.room_id +ORDER BY num_rows desc +LIMIT 10; +
This document aims to get you started with contributing to Synapse!
By following the upstream support life cycles Synapse can ensure that its dependencies continue to get security patches, while not requiring system admins to constantly update their platform dependencies to the latest versions.