Add compose.host-ports.yml #4
@ -12,3 +12,6 @@ COMPOSE_FILE="compose.yml"
|
||||
|
||||
## Web client
|
||||
#COMPOSE_FILE="$COMPOSE_FILE:compose.mumbleweb.yml"
|
||||
|
||||
## Host-port mode
|
||||
|
|
||||
#COMPOSE_FILE="$COMPOSE_FILE:compose.host-ports.yml"
|
||||
|
||||
21
README.md
21
README.md
@ -50,6 +50,27 @@ overlay. To enable it:
|
||||
2. `abra app deploy <YOURAPPDOMAIN> --force`
|
||||
3. Open `https://<YOURAPPDOMAIN>` in a browser
|
||||
|
||||
|
||||
## Host-Port Mode
|
||||
|
||||
Instead of modifying the Traefik config,
|
||||
you can alternatively deploy Mumble with compose.host-ports.yml,
|
||||
and it will bind directly to the host server port 64738,
|
||||
amras
commented
I don't think 64739 is used anywhere. I don't think 64739 is used anywhere.
notplants
commented
lol you are correct. I was somehow morphing this in my mind with lasuite-meet which does you multiple ports, and the fact that there were two entries (one for tcp and udp) glad to have a second pair of eyes on it lol you are correct.
I was somehow morphing this in my mind with lasuite-meet which does you multiple ports, and the fact that there were two entries (one for tcp and udp)
glad to have a second pair of eyes on it
|
||||
bypassing Traefik.
|
||||
|
||||
This is not recommended for multinode setups, since the client would have to connect directly to whichever node is running the app container, but this does work when deployed to a single server.
|
||||
|
amras
commented
I wonder if we should be more specific here? In principle, there's nothing stopping a multinode setup from using host ports, as long as the operator locks deployment to specific nodes. But it will break in the typical swarm setup with interchangeable worker nodes. Maybe something like:
What are your thoughts? I wonder if we should be more specific here?
In principle, there's nothing stopping a multinode setup from using host ports, as long as the operator locks deployment to specific nodes. But it will break in the typical swarm setup with interchangeable worker nodes.
Maybe something like:
> This is not recommended for multinode setups, since the client would have to connect directly to whichever node is running the app container.
What are your thoughts?
notplants
commented
Your phrasing seems good to me. I changed it. Your phrasing seems good to me. I changed it.
|
||||
|
||||
With this compose file, you can deploy mumble without any changes to the Traefik config:
|
||||
|
||||
1. `abra app config <YOURAPPDOMAIN>` — uncomment the line:
|
||||
```
|
||||
COMPOSE_FILE="$COMPOSE_FILE:compose.host-ports.yml"
|
||||
```
|
||||
2. `abra app deploy <YOURAPPDOMAIN>`
|
||||
|
||||
|
||||
|
||||
|
||||
[`abra`]: https://git.coopcloud.tech/coop-cloud/abra
|
||||
[`coop-cloud/traefik`]: https://git.coopcloud.tech/coop-cloud/traefik
|
||||
[Mumble client]:(https://www.mumble.info/downloads/)
|
||||
|
||||
14
compose.host-ports.yml
Normal file
14
compose.host-ports.yml
Normal file
@ -0,0 +1,14 @@
|
||||
---
|
||||
version: "3.8"
|
||||
|
||||
services:
|
||||
app:
|
||||
ports:
|
||||
- target: 64738
|
||||
published: 64738
|
||||
protocol: tcp
|
||||
mode: host
|
||||
- target: 64738
|
||||
published: 64738
|
||||
protocol: udp
|
||||
mode: host
|
||||
Reference in New Issue
Block a user
What are your thoughts on including a configurable port number in the config?
Upside: this would trivially allow multiple deployments on the same server, as long as each had a unique port.
Downside: might be confusing to the operator, especially since the port number would only be configurable in host-port mode.
I could see adding this, but maybe in a separate PR? could also in that PR think on if there is a way to also make it configurable in traefik mode somehow, at the same time.
But I think manually harcoding the port like this probably covers the majority of usecases