Erik JohnstonandClaude Fable 5
429baac202
- get_thread_id/main_thread claimed to return an 'OS thread id'; restore the historical caveat that threading.get_ident is not an OS tid and is stable across Synapse's single fork() (which is also why the new per-thread cache stays correct across it). - Explain skip_from_py_object on ContextResourceUsage (pyo3 0.28 makes the Clone-pyclass FromPyObject opt-in/out explicit; we build -D warnings). - Note that __repr__ diverges from the historical Python repr for exponent-form floats, and that main_thread is settable only for tests. - Promote create_deferred's cancellation limitation to a TODO and cross-reference run_python_awaitable's finished-context defence. - Carry the dropped Python docstrings into the .pyi stub (start/stop 'do not call directly', get_resource_usage returns a *copy*, __init__ args, the sentinel usage guidance), and note that tag is typed str while the runtime deliberately also accepts None. - tests: fix the stale rust/src/logcontext.rs path, explain why 'synapse' is in _RUST_LOGGER_ROOTS (the crate is named synapse) and the Python- namespace collision hazard, drop a stale deferred.rs:223 FIXME reference, explain the 50000-iteration pump bound, and rename prepare's parameter to match the base class (pyright). - docs: name the helper (LogContext::capture/scope) instead of 'the provided helper'. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JFbRtswu7rsHrttJFauUUb
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.
Synapse configuration documentation
The Configuration Manual page is generated from a YAML file, schema/synapse-config.schema.yaml. To add new options or modify existing ones, first edit that file, then run scripts-dev/gen_config_documentation.py to generate an updated Configuration Manual markdown file.
Build the book as described above to preview it in a web browser.
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.