Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Landing.md - add info on how to use extra_well_known_client_content in homeserver.yaml #443

Merged
merged 1 commit into from
Jun 5, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion docs/Landing.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,12 +4,18 @@ Welcome intrepid Matrix explorer. You've landed on this page because you're tryi

- Configure Postgres and install a sliding sync proxy as described in the [docs](https://github.com/matrix-org/sliding-sync).
- Advertise the proxy by configuring an [`org.matrix.msc3575.proxy`](https://github.com/matrix-org/matrix-spec-proposals/blob/kegan/sync-v3/proposals/3575-sync.md#unstable-prefix) property in the server's `/.well-known/matrix/client` config:
```
```json
{
"org.matrix.msc3575.proxy": {
"url": "https://slidingsync.proxy.url.here"
}
}
```
You can do this by adding the following to your homeserver.yaml:
```yaml
extra_well_known_client_content:
"org.matrix.msc3575.proxy":
"url": "https://slidingsync.proxy.url.here"
```

Once these steps are complete you will be able to continue on your journey of exploring the very latest that Matrix has to offer!
Loading