Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatically reload SSL certificate on change #5987

Closed
dabruh opened this issue Dec 9, 2022 · 1 comment
Closed

Automatically reload SSL certificate on change #5987

dabruh opened this issue Dec 9, 2022 · 1 comment
Labels
feature-request This issue or PR deals with a new feature triage This issue is waiting to be triaged by one of the project members

Comments

@dabruh
Copy link

dabruh commented Dec 9, 2022

Context

Seamless integration in containerized environments

Description

We currently support Live reload of Murmur SSL settings via SIGUSR1, but I struggle to figure out how we can automatically send this SIGUSR1 signal in a scenario where we're running two Docker Compose services (containers) where one is the Mumble server, and another a container that handles the certificate renewal against a shared volume of the two containers.

I thus propose that the Mumble server does periodic checking (or listens for FS events) of the SSL certificate file and automatically tries to reload it when it's modified.

This is related to mumble-voip/mumble-docker#28

Mumble component

Server

OS-specific?

No

Additional information

No response

@dabruh dabruh added feature-request This issue or PR deals with a new feature triage This issue is waiting to be triaged by one of the project members labels Dec 9, 2022
@Krzmbrzl
Copy link
Member

Duplicate of #4544

@Krzmbrzl Krzmbrzl closed this as not planned Won't fix, can't repro, duplicate, stale Dec 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request This issue or PR deals with a new feature triage This issue is waiting to be triaged by one of the project members
Projects
None yet
Development

No branches or pull requests

2 participants