Conversation
|
Why do we do this though? |
|
So there are "external" and "internal" listeners. The external listeners are where In monolith mode, we were previously defaulting to both listeners being the same, so In polylith mode, whether a component starts both external+internal listeners or just the internal listener depends on whether it has public-facing APIs (like the client API, sync API, federation API, media API) or not. This PR changes things around so that the internal listener now listens on |
internal/setup/base.go
Outdated
| const HTTPClientTimeout = time.Second * 30 | ||
|
|
||
| const NoInternalListener = "" | ||
| const NoExternalListener = "" |
There was a problem hiding this comment.
What's going on here? You need some actual values here else NoInternalListener is the same as NoExternalListener - https://play.golang.org/p/bIAL8JumJtK
There was a problem hiding this comment.
They're just designed to be human-readable rather than leaving "" littered about the place, e.g.
dendrite/cmd/dendrite-monolith-server/main.go
Lines 164 to 168 in 759bab6
dendrite/cmd/dendrite-room-server/main.go
Lines 35 to 39 in 759bab6
This makes some changes to the monolith
-apibehaviour:localhost:18008by default when-apiis enabled-api-bind-addressfor overriding the aboveThis probably requires a patch to Sytest to set
-api-bind-addressto something non-conflicting when we use-api.