coop-cloud/mumble
1
0
Fork 0
Code Issues 2 Pull Requests 1 Projects Releases Wiki Activity

Add compose.host-ports.yml #4

Manually merged
amras merged 3 commits from host-ports into main 2026-05-01 11:10:13 +00:00
Conversation 4 Commits 3 Files Changed 3 +38
notplants commented 2026-04-28 15:59:19 +00:00
Owner
Copy Link

based on conversation here: #1 (comment)

based on conversation here: https://git.coopcloud.tech/coop-cloud/mumble/pulls/1#issuecomment-33149
notplants added 2 commits 2026-04-28 15:59:19 +00:00
add compose.host-ports.yml for optional direct host port publishing 5f66e5ba2d
Update readme to describe host-ports mode
Some checks failed
continuous-integration/drone/pr Build is failing
Details
a707387872
notplants commented 2026-04-28 16:01:26 +00:00
Author
Owner
Copy Link

I have locally tested this PR and seems to be working

(in addition to running the similar PR #1 here for one month, which is working)

I have locally tested this PR and seems to be working (in addition to running the similar PR https://git.coopcloud.tech/coop-cloud/mumble/pulls/1 here for one month, which is working)
amras requested changes 2026-04-30 09:48:32 +00:00
.env.sample
@ -13,2 +13,4 @@
## Web client
#COMPOSE_FILE="$COMPOSE_FILE:compose.mumbleweb.yml"
## Host-port mode
amras commented 2026-04-30 09:45:43 +00:00
Owner
Copy Link

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.

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.
notplants commented 2026-04-30 16:20:01 +00:00
Author
Owner
Copy Link

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

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
README.md Outdated
@ -53,0 +55,4 @@
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 ports 64738 and 64739,
amras commented 2026-04-30 09:47:24 +00:00
Owner
Copy Link

I don't think 64739 is used anywhere.

I don't think 64739 is used anywhere.
notplants commented 2026-04-30 16:14:46 +00:00
Author
Owner
Copy Link

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
README.md Outdated
@ -53,0 +58,4 @@
and it will bind directly to the host server ports 64738 and 64739,
bypassing Traefik.
Note this doesn't work in multinode setups, but does work when deployed to a single server.
amras commented 2026-04-30 09:39:52 +00:00
Owner
Copy Link

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?

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 2026-04-30 16:16:34 +00:00
Author
Owner
Copy Link

Your phrasing seems good to me. I changed it.

Your phrasing seems good to me. I changed it.
notplants added 1 commit 2026-04-30 16:18:08 +00:00
update readme to fix error
Some checks failed
continuous-integration/drone/pr Build is failing
Details
8530a5fae2
notplants commented 2026-04-30 16:20:45 +00:00
Author
Owner
Copy Link

fixed the port error in the readme, and updated it to include your phrasing about multinode @amras

fixed the port error in the readme, and updated it to include your phrasing about multinode @amras
amras manually merged commit 7ee486c156 into main 2026-05-01 11:10:13 +00:00
amras commented 2026-05-01 11:12:24 +00:00
Owner
Copy Link

While resolving merge conflicts, I noticed we might want to document the new option in .env, too. I let myself add a short summary there.

While resolving merge conflicts, I noticed we might want to document the new option in .env, too. I let myself add a short summary there.
Sign in to join this conversation.
Reviewers
No Reviewers
amras
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
3wordchant aadil abra-bot ammaratef45 amras BornDeleuze cas coopcloud decentral1se fauno jjsfunhouse kawaiipunk knoflook moosemower notplants oxaliq p4u1 renovate-bot stevensting trav yksflip
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coop-cloud/mumble#4
No description provided.
Delete Branch "host-ports"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?