Request for Documentation: Update incorrect documentation for `WebsocketPort` and `WebsocketSecurePort` settings

[mm-cloud-bot]

Mattermost user claudio.costa from https://community.mattermost.com has requested the following be documented:

As noted, both `WebsocketPort` and `WebsocketSecurePort` are purely client-side properties. The listening address for WebSocket is the same for the main HTTP API and controlled by `ServiceSettings.ListenAddress`. I'll file a ticket to update the documentation.

See the original post here.

This issue was generated from Mattermost using the Doc Up plugin.

[cwarnermm]

Thanks, @streamer45! Given that these are client-side properties, what specifically should we call out via the product documentation? Under what circumstances would an admin set these client-side configs and what do admins need to know about working with these configs in general?

[streamer45]

Thanks, @streamer45! Given that these are client-side properties, what specifically should we call out via the product documentation? Under what circumstances would an admin set these client-side configs and what do admins need to know about working with these configs in general?

@cwarnermm Apologies for not adding context. I actually created an internal ticket (https://mattermost.atlassian.net/browse/MM-51523) to have someone from the team take care of this. We'll open a PR when ready and ping you there for final review.

[cwarnermm]

Thanks so much, @streamer45! Really appreciate the Engineering support on this documentation issue.