MatrixSynapse/docs
Tadeusz Sośnierz 1433b5d5b6
Show erasure status when listing users in the Admin API (#14205)
* Show erasure status when listing users in the Admin API

* Use USING when joining erased_users

* Add changelog entry

* Revert "Use USING when joining erased_users"

This reverts commit 30bd2bf106.

* Make the erased check work on postgres

* Add a testcase for showing erased user status

* Appease the style linter

* Explicitly convert `erased` to bool to make SQLite consistent with Postgres

This also adds us an easy way in to fix the other accidentally integered columns.

* Move erasure status test to UsersListTestCase

* Include user erased status when fetching user info via the admin API

* Document the erase status in user_admin_api

* Appease the linter and mypy

* Signpost comments in tests

Co-authored-by: Tadeusz Sośnierz <tadeusz@sosnierz.com>
Co-authored-by: David Robertson <david.m.robertson1@gmail.com>
2022-10-21 13:52:44 +01:00
..
admin_api Show erasure status when listing users in the Admin API (#14205) 2022-10-21 13:52:44 +01:00
changelogs
development Handle `gottestfmt` repository move (#14144) 2022-10-11 17:54:06 +00:00
modules
other
privacy_policy_templates/en
setup Update NixOS module URL (#13818) 2022-09-26 15:26:59 +01:00
systemd-with-workers Add sample worker files for `pusher` and `federation_sender` (#14077) 2022-10-07 14:25:28 +01:00
usage Document encryption_enabled_by_default_for_room_type under the right name (#14110) 2022-10-19 20:17:37 +01:00
website_files
.sample_config_header.yaml
CAPTCHA_SETUP.md
README.md
SUMMARY.md Add monthly active users documentation (#13617) 2022-09-01 14:48:43 +00:00
ancient_architecture_notes.md
application_services.md
architecture.md
auth_chain_diff.dot
auth_chain_diff.dot.png
auth_chain_difference_algorithm.md
code_style.md
consent_tracking.md
delegate.md
deprecation_policy.md Define SQLite compat policy (#13728) 2022-09-07 12:07:42 +00:00
favicon.png
favicon.svg
federate.md
jwt.md
log_contexts.md
manhole.md
media_repository.md
message_retention_policies.md
metrics-howto.md Improve the listener example on the metrics documentation (#14078) 2022-10-07 14:54:01 +01:00
openid.md Document Google OpenID Connect email attribute (#14081) 2022-10-07 14:22:25 +00:00
opentracing.md
password_auth_providers.md
postgres.md
presence_router_module.md
replication.md
reverse_proxy.md Be able to correlate timeouts in reverse-proxy layer in front of Synapse (pull request ID from header) (#13801) 2022-09-15 15:32:25 -05:00
room_and_user_statistics.md
sample_config.yaml
sample_log_config.yaml
server_notices.md
spam_checker.md
sso_mapping_providers.md Correct documentation for map_user_attributes of OpenID Mapping Providers (#13836) 2022-09-21 13:08:16 +00:00
structured_logging.md
synctl_workers.md
tcp_replication.md
templates.md
turn-howto.md
upgrade.md Deprecate the `generate_short_term_login_token` method in favor of an async `create_login_token` method in the Module API. (#13842) 2022-10-06 10:22:36 +00:00
user_directory.md
welcome_and_overview.md
workers.md Stabilize the threads API. (#14175) 2022-10-14 07:16:50 -04:00

README.md

Synapse Documentation

The documentation is currently hosted here. Please update any links to point to the new website instead.

About

This directory currently holds a series of markdown files documenting how to install, use and develop Synapse. The documentation is readable directly from this repository, but it is recommended to instead browse through the website for easier discoverability.

Adding to the documentation

Most of the documentation currently exists as top-level files, as when organising them into a structured website, these files were kept in place so that existing links would not break. The rest of the documentation is stored in folders, such as setup, usage, and development etc. All new documentation files should be placed in structured folders. For example:

To create a new user-facing documentation page about a new Single Sign-On protocol named "MyCoolProtocol", one should create a new file with a relevant name, such as "my_cool_protocol.md". This file might fit into the documentation structure at:

  • Usage
    • Configuration
      • User Authentication
        • Single Sign-On
          • My Cool Protocol

Given that, one would place the new file under usage/configuration/user_authentication/single_sign_on/my_cool_protocol.md.

Note that the structure of the documentation (and thus the left sidebar on the website) is determined by the list in SUMMARY.md. The final thing to do when adding a new page is to add a new line linking to the new documentation file:

- [My Cool Protocol](usage/configuration/user_authentication/single_sign_on/my_cool_protocol.md)

Building the documentation

The documentation is built with mdbook, and the outline of the documentation is determined by the structure of SUMMARY.md.

First, get mdbook. Then, from the root of the repository, build the documentation with:

mdbook build

The rendered contents will be outputted to a new book/ directory at the root of the repository. Please note that index.html is not built by default, it is created by copying over the file welcome_and_overview.html to index.html during deployment. Thus, when running mdbook serve locally the book will initially show a 404 in place of the index due to the above. Do not be alarmed!

You can also have mdbook host the docs on a local webserver with hot-reload functionality via:

mdbook serve

The URL at which the docs can be viewed at will be logged.

Configuration and theming

The look and behaviour of the website is configured by the book.toml file at the root of the repository. See mdbook's documentation on configuration for available options.

The site can be themed and additionally extended with extra UI and features. See website_files/README.md for details.