coturn VS awesome-compose

Stars: 11875 Author: coturn Star the coturn repository⭐

Might work with coturn or turn-rs, others?

https://github.com/coturn/coturn

https://github.com/mycrl/turn-rs

Maybe there are some projects doing only stun - if that is enough?

Both TURN and STUN can be self hosted, the most popular project i have found is coturn

# TURN server name and realm realm=DOMAIN server-name=turnserver # Use fingerprint in TURN message fingerprint # IPs the TURN server listens to listening-ip=0.0.0.0 # External IP-Address of the TURN server external-ip=IP_ADDRESS # Main listening port listening-port=3478 # Further ports that are open for communication min-port=10000 max-port=20000 # Log file path log-file=/var/log/turnserver.log # Enable verbose logging verbose # Specify the user for the TURN authentification user=turnuser:turn456 # Enable long-term credential mechanism lt-cred-mech # If running coturn version older than 4.5.2, uncomment these rules and ensure # that you have listening-ip set to ipv4 addresses only. # Prevent Loopback bypass https://github.com/coturn/coturn/security/advisories/GHSA-6g6j-r9rf-cm7p #denied-peer-ip=0.0.0.0-0.255.255.255 #denied-peer-ip=127.0.0.0-127.255.255.255 #denied-peer-ip=::1

I am trying to deploy coturn server in the Kubernetes cluster.

That is an excellent use case for a webrtc server rather than an usual voice communication. If you decide to go that way, you don't need any sim card. You just need an internet access. You install a webrtc client (the usual one is coturn). I don't know if you also need to set up some kind of chat server in addition.

I've found this issue for you: https://github.com/coturn/coturn/issues/492

If you host yourself on a VPS you can hook in coturn (it's enabled by the linked playbook by default):

https://github.com/spantaleev/matrix-docker-ansible-deploy/b...

https://github.com/coturn/coturn

Docker Compose Samples — ready-made stacks to learn from

Docker Compose Samples prebuilt examples for common stacks

These tricks—profiles, environment overrides, build caching, healthchecks, custom logs, named volumes, and file extensions—can transform how you use Docker Compose. They save time, reduce errors, and make your workflows more flexible. Try them in your next project, starting with profiles or healthchecks to see immediate wins. Check the Docker Compose documentation for deeper dives, and experiment with these examples to tailor them to your stack.

Docker Compose for local development environments

This removes all container volumes and resets everything to its initial state. See the official documentation for more details.

This tutorial assumes familiarity with Docker, Docker Compose, Devcontainers and that your services have Dockerfile implemented

Docker Compose Docs

I talk a lot about using containers for local development. The container that I always used was some running LLM container that I pulled from the Docker Hub official AI image registry. I initially started dev work by just running npm start to get my app running and test connecting to a container, and then I got more savvy with my approach by leveraging Docker Compose. Docker Compose allowed me to automatically spin up my containers, set up port mapping, and even run a post_start command on my LLM container to pull the correct model.

Docker includes a secrets management solution, but it doesn't work with standalone containers. You can supply secrets to your containers when you're using either Docker Compose or Docker Swarm. There's no alternative for containers created manually with a plain docker run command.

Docker Compose Docs: Essential for orchestrating multi-container environments and scaling test runners.