https://git.coopcloud.tech/coop-cloud/snikket/src/commit/505a0f550c875506f5a33505dc0743eed078b3ac/compose.yml#L103-L111 vs. what https://github.com/snikket-im/snikket-server/blob/master/docs/advanced/firewall.md#ports says - do we need some generation script to get the hardcoding going for the ports?
If you follow #6 (comment) and config an external coturn (not setup in the recipe yet but simple to do) then you can avoid all these port settings. This could be setup nicely in a compose.yml/compose.turn.yml config soon. Doesn't solve the core problem of this ticket ofc but is a work-around.
If you follow https://git.coopcloud.tech/coop-cloud/snikket/issues/6#issuecomment-11268 and config an external coturn (not setup in the recipe yet but simple to do) then you can avoid all these port settings. This could be setup nicely in a `compose.yml`/`compose.turn.yml` config soon. Doesn't solve the core problem of this ticket ofc but is a work-around.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Did add
If you follow #6 (comment) and config an external coturn (not setup in the recipe yet but simple to do) then you can avoid all these port settings. This could be setup nicely in a
compose.yml/compose.turn.ymlconfig soon. Doesn't solve the core problem of this ticket ofc but is a work-around.