Files
mesh-host/testdata/beside/mesh-catalog/modules/matrix/files/conduit.toml
T
jschoubben d68e241724 Take the catalogue's composition rules into the node-engine
ADR 0593 §7: the composer with its refusals leaves mesh-sdk, so mesh-sdk
carries no composition rule. The catalogue functions only the
node-engine's composition reaches (Resolve, Resolution's Compose,
Declaration, DataItems, LeftOut, Rules and the rest, the settings,
placeholder and template refusals, the rendering helpers) are copied
with their tests into internal/compose/resolution; a method of a
mesh-sdk shape becomes a function taking it first. The composition
calls its own copies, and the captured catalogue its tests read lives
here now, shared by mesh-compose's tests.

Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL
2026-11-02 19:15:55 +01:00

16 lines
665 B
TOML

# Written by the mesh (modules/matrix). Conduit reads this file (CONDUIT_CONFIG); nothing comes
# from the environment. server_name is the homeserver's permanent identity: every user id, room id
# and signature in the database carries it, so it is the name this module is served under
# (${bound:route:name-homeserver}) and never changes once a database exists.
[global]
server_name = "${bound:route:name-homeserver}"
database_backend = "rocksdb"
database_path = "/var/lib/matrix-conduit/"
address = "0.0.0.0"
port = 6167
max_request_size = 20000000
allow_registration = false
allow_federation = true
allow_check_for_updates = true
trusted_servers = ["matrix.org"]