Skip to content

Update an external reference to matrix synapse documentation #951

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.

Sign up for GitHub

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

Open
frlan wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update an external reference to matrix synapse documentation #951

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
1 change: 1 addition & 0 deletions changelog.d/961.doc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Update a link in documentation to reflect changes in organisation of Matrix Synapse upstream project.
4 changes: 2 additions & 2 deletions docs/setup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ Copy `registration.sample.yml` into `registration.yml` and fill in:
At a minimum, you will need to replace the `as_token` and `hs_token` and change the domain part of the namespaces. The sample config can be also found at our [github repo](https://raw.githubusercontent.com/matrix-org/matrix-hookshot/main/registration.sample.yml) for your convienence.

You will need to link the registration file to the homeserver. Consult your homeserver documentation
on how to add appservices. [Synapse documents the process here](https://matrix-org.github.io/synapse/latest/application_services.html).
on how to add appservices. [Synapse documents the process here](https://element-hq.github.io/synapse/latest/application_services.html).

### Homeserver Configuration

Expand Down Expand Up @@ -235,7 +235,7 @@ This will pass all requests at `/widgetapi` to Hookshot.
In terms of API endpoints:

- The `webhooks` resource handles resources under `/`, so it should be on its own listener.
Note that OAuth requests also go through this listener. Previous versions of the bridge listened for requests on `/` rather than `/webhook`. While this behaviour will continue to work, administators are advised to use `/webhook`.
Note that OAuth requests also go through this listener. Previous versions of the bridge listened for requests on `/` rather than `/webhook`. While this behaviour will continue to work, administators are advised to use `/webhook`.
- The `metrics` resource handles resources under `/metrics`.
- The `provisioning` resource handles resources under `/v1/...`.
- The `widgets` resource handles resources under `/widgetapi/v1...`. This may only be bound to **one** listener at present.
Expand Down