342f0c35b7
Added RHEL/Rocky install instructions (PyPI). Instructions cover versions 8 and 9 which are the only supported ones - except for RHEL7 which is now on extended life cycle support phase. Large part of the guide is for installing Python 3.11 or 3.12. RHEL8 ships with Python 3.6 and RHEL9 ships with 3.9. Newer Python versions can be installed easily as they don't interfere with OS software that still relies on the default Python version. I was first planning to add prerequisites part to the prerequisites section and then install instructions on the top of the page but that section is for pre-built packages so it just didn't sound right. So I just dumped everything to the PyPI section of the page. But suggestions to change are welcome. I also didn't combine these with Fedora section. I haven't tested those packages on RHEL and Fedora ships with Python 3.12 out-of-box. |
||
---|---|---|
.. | ||
admin_api | ||
changelogs | ||
development | ||
modules | ||
other | ||
privacy_policy_templates/en | ||
setup | ||
systemd-with-workers | ||
usage | ||
website_files | ||
.sample_config_header.yaml | ||
ancient_architecture_notes.md | ||
application_services.md | ||
architecture.md | ||
auth_chain_diff.dot | ||
auth_chain_diff.dot.png | ||
auth_chain_difference_algorithm.md | ||
CAPTCHA_SETUP.md | ||
code_style.md | ||
consent_tracking.md | ||
delegate.md | ||
deprecation_policy.md | ||
element_logo_white_bg.svg | ||
favicon.png | ||
favicon.svg | ||
federate.md | ||
jwt.md | ||
log_contexts.md | ||
manhole.md | ||
media_repository.md | ||
message_retention_policies.md | ||
metrics-howto.md | ||
openid.md | ||
opentracing.md | ||
password_auth_providers.md | ||
postgres.md | ||
presence_router_module.md | ||
README.md | ||
replication.md | ||
reverse_proxy.md | ||
room_and_user_statistics.md | ||
sample_config.yaml | ||
sample_log_config.yaml | ||
server_notices.md | ||
spam_checker.md | ||
sso_mapping_providers.md | ||
structured_logging.md | ||
SUMMARY.md | ||
synctl_workers.md | ||
tcp_replication.md | ||
templates.md | ||
turn-howto.md | ||
upgrade.md | ||
user_directory.md | ||
welcome_and_overview.md | ||
workers.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
- Single Sign-On
- User Authentication
- Configuration
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.