-
Notifications
You must be signed in to change notification settings - Fork 70
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
Docs and config improvements #124
Conversation
This reverts commit b422b3d.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
some comments
|
||
You will also need to make this port accessible to the internet so services like GitHub can reach the bridge. It | ||
is recommended to factor hookshot into your load balancer configuration, but currrently this process is left as an | ||
excercise to the user. | ||
|
||
In terms of API endpoints: | ||
|
||
- The `webhooks` resource handles resources under `/`, so it should be on it's own listener. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should be on its on listener
but you can reasonably assume that webhooks will not get assigned an endpoint /metrics
or /v1...
.... right?!
|
||
You will also need to make this port accessible to the internet so services like GitHub can reach the bridge. It | ||
is recommended to factor hookshot into your load balancer configuration, but currrently this process is left as an | ||
excercise to the user. | ||
|
||
In terms of API endpoints: | ||
|
||
- The `webhooks` resource handles resources under `/`, so it should be on it's own listener. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
*its
bindAddress: 127.0.0.1 | ||
``` | ||
|
||
The `port` and `bindAddress` must not conflict with the other listeners in the bridge config. This listeners should **not** be reachable |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
*listener
# | ||
domain: example.com | ||
url: http://localhost:8008 | ||
mediaUrl: http://example.com |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
perhaps it would be reasonable to explain:
- domain: "name" of your homeserver, as it appears in your MXIDs
- url: where hs is reachable, preferably internally i.e. localhost => docker needs adjustment
- mediaUrl: homeserver, but via potential load balancer etc to reach the media worker(?)
- port & bindAddress need adjustment/forwarding when using docker
@Half-Shot not sure if this shows up in your notifs, hence ping: please look over these comments |
Fixes #120
Fixes #123