Updating the mumble recipe #1

Open
notplants wants to merge 3 commits from newmumble into main
Owner

autonomic mumble from the old times was having issues, so decided to update the recipe to the latest to host our own

appears to be working. was able to use same port publishing pattern I was using in another recipe recently for lasuite-meet

addition of a web client was a nice bonus

autonomic mumble from the old times was having issues, so decided to update the recipe to the latest to host our own appears to be working. was able to use same port publishing pattern I was using in another recipe recently for lasuite-meet addition of a web client was a nice bonus
notplants added 3 commits 2026-03-03 20:19:07 +00:00
add backups
Some checks failed
continuous-integration/drone/pr Build is failing
a1a5e2adac
Author
Owner

the old 3 year update cycle ... I assume this is probably fine to merge but cc @3wordchant

the old 3 year update cycle ... I assume this is probably fine to merge but cc @3wordchant
3wordchant requested changes 2026-03-04 19:07:45 +00:00
@ -11,0 +15,4 @@
# Mumble uses its own protocol on port 64738 (TCP+UDP), not HTTP.
# Published directly on the host — cannot be proxied through Traefik
# without custom entrypoints.
ports:
Owner
Benefits of this over https://git.coopcloud.tech/coop-cloud/traefik/src/branch/master/compose.mumble.yml?
Owner

Update looks good. Personally it seems confusing not to centralise port config in Traefik but 🤷

Update looks good. Personally it seems confusing not to centralise port config in Traefik but 🤷
Author
Owner

@3wordchant ty for taking a look. I see pros/cons of each approach to the ports thing

pro of centralizing in traefik is:

  • if you show up at a new server and want to figure out the port config its all in one place to find

pro of the port config in the recipe is:

  • mumble recipe is self-contained. you can just setup the mumble env and deploy without making any changes to traefik (this is the main reason I liked this approach, as to me it made it easier to setup and deploy)
@3wordchant ty for taking a look. I see pros/cons of each approach to the ports thing pro of centralizing in traefik is: - if you show up at a new server and want to figure out the port config its all in one place to find pro of the port config in the recipe is: - mumble recipe is self-contained. you can just setup the mumble env and deploy without making any changes to traefik (this is the main reason I liked this approach, as to me it made it easier to setup and deploy)
Owner

Maybe let's discuss in #coopcloud-tech? I see the "easier" argument (although uncommenting 1 line in abra app config traefik... and redeploying it doesn't seem nightmarish in the scheme of things) but it feels like apps opening their own ports might be unexpected security-wise.

Maybe let's discuss in `#coopcloud-tech`? I see the "easier" argument (although uncommenting 1 line in `abra app config traefik...` and redeploying it doesn't seem nightmarish in the scheme of things) but it feels like apps opening their own ports might be unexpected security-wise.
Author
Owner

@3wordchant want to link this PR into the #coopcloud-tech chat?

I guess for me, as I was trying to understand a recipe, I found it unexpected when there was "action at a distance" and there were also necessary related code changes in another recipe (traefik), even if small. having to touch two repositories instead of one. but I'm not sure how to weigh the approach either way for security

@3wordchant want to link this PR into the #coopcloud-tech chat? I guess for me, as I was trying to understand a recipe, I found it unexpected when there was "action at a distance" and there were also necessary related code changes in another recipe (traefik), even if small. having to touch two repositories instead of one. but I'm not sure how to weigh the approach either way for security
Author
Owner

more host port half-related stuff here: coop-cloud/traefik#88

more host port half-related stuff here: https://git.coopcloud.tech/coop-cloud/traefik/pulls/88
Some checks failed
continuous-integration/drone/pr Build is failing
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin newmumble:newmumble
git checkout newmumble
Sign in to join this conversation.
No description provided.