docker-jitsi-meet
Kong
docker-jitsi-meet | Kong | |
---|---|---|
9 | 18 | |
2,950 | 37,537 | |
1.1% | 0.7% | |
9.2 | 9.9 | |
3 days ago | 3 days ago | |
Lua | Lua | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
docker-jitsi-meet
-
List of your reverse proxied services
Jitsi Meet for selfhosted Video Meetings
-
Needs help with jitsi
With this version I am facing the same issue as describef by you. This version is broken: https://github.com/jitsi/docker-jitsi-meet/issues/1377
-
Looking for foss voip software with screen sharing?
Most video conferencing suites allow starting a call with video disabled so they don't block you from using only audio all the time. Most video suites will also provide either a docker container or suite of containers via docker-compose to get you started quickly. Personally, I host Jitsi using https://github.com/jitsi/docker-jitsi-meet. If you want to try before you host then you can use https://meet.jit.si/ which is the free/public Jitsi instance. They don't require accounts to try. When you host it yourself, there's even an end-to-end encryption option you can enable.
-
Jitsi + Nginx Proxy Manager + Wireguard
proxy_http_version 1.1 may not be necessary. I copied it from the nginx configuration files included in the official jitsi docker images. I think they are making sure that no HTTP 1.0 requests are made because websockets aren't supported on 1.0. It would be rare for a device to use 1.0 these days, though.
-
Jitsi Config File Confusion
If you need to configure options that are not supported through the ".env" file then, first, be sure to open an issue because the Jitsi maintainers intend for ".env" to manage all the configurations. From there, you can inject only your configuration overrides for the config.json by mounting it in your container as "/config/custom-config.json". This would look like a ' - "/path/to/my/config.json:/config/custom-config.json' entry in the "volumes" section of your docker compose. See https://github.com/jitsi/docker-jitsi-meet/issues/768 for a discussion on this.
-
coTurn Docker Setup
https://github.com/jitsi/docker-jitsi-meet/blob/master/docker-compose.yml <-- this is the docker-compose.yml in the official repository, did you tried it?
-
Friendly reminders
download the latest release from https://github.com/jitsi/docker-jitsi-meet/releases (at time of writing stable-6173: release)
-
Zoom vs MS Teams for Security
+1 Jitsi, but host it yourself! This is the Docker install that let's you customize the experience. Browser or app based, platform-agnostic, fully encrypted back to your container, with the option to register a SIP endpoint for people to be able to dial into the conference via your IP PBX and do audio-only conferencing. Jitsi does ALMOST everything that Teams / Zoom can do but for regular conferences with screen sharing, it's hard to beat. I built a web scheduler that initializes meetings via JWT so no inadvertent meetings can start without the organizer, solving one of the drawbacks.
-
Do I need to host my own jitsi server for it to be private? Is there an easy guide on how to do it? I am not tech savvy
Jitsi is pretty secure and private with using meet.jit.si their server. Also it supports all the devices Android IOS PC and Mac. For your small group I would give it a shot and see what you think. As for server, yes it can be done - https://www.osradar.com/deploy-jitsi-meet-server-with-docker/ or https://github.com/jitsi/docker-jitsi-meet I had issues with Android getting connected so we just use meet.jit.si and it all works fine with 3 people.
Kong
- Kong 3.6 with LLM Support
-
5 Ways to Improve Your API Reliability
Kong: A cloud-native, fast, scalable, and distributed Microservice Abstraction Layer (also known as an API Gateway or API Middleware). Made available as an open-source project in 2015, its core functionality is written in Lua and it runs on the nginx web server.
-
Access to Gravitee Github repository has been restricted - This is NOT how OSS works
OPeNsOuRcE. Good time to switch to Kong, better option anyways.
- Self hosting costing questions
-
Proxy Basic Auth Replacement Best Practice for Cloud Native / OIDC / Vault
Sounds like you want an API gateway? What about Kong?
-
HAProxy 2.7
Unquestionably no, Kong is "OpenResty plus a management plane" and they're Apache 2: https://github.com/kong/kong#license
-
Ask HN: Who is hiring? (April 2022)
Kong (https://konghq.com) | Gateway Senior Engineer | REMOTE Europe | Full-time
The Kong Gateway is an API Management solution, which serves as a foundation for many other solutions by the company. The business model is open-core: an Open Source solution exists (https://github.com/kong/kong), and there's an Enterprise version with more features and dedicated support.
The tech stack is a modified Openresty with of Lua code on top. The ideal candidate would be someone who is already familiar with Kong. Alternatively, if you are familiar with Openresty or other API management solution, we also would love to talk with you.
I am personally interested in finding people to join me in the European Gateway Team. The role involves adding features, fixing bugs, and collaborating with other teams. Here's that position:
https://jobs.lever.co/kong/c1a2b204-45a8-4c19-9cd4-d9824a778...
We have many projects and many teams all around the world (current headcount is ~450), using other technologies like Node in the Kong Manager or Go in the Koko project, and we are constantly looking for people. Please visit our careers page to find out more!
https://konghq.com/careers/
-
Breaking Up a Monolithic Database with Kong
Kong Gateway allows the complexity of service-tier APIs to be reduced to a collection of endpoints (or URIs) focused on meeting a collection of business needs and functionality. Often-duplicated components (like authentication, logging, and security) are handled by the gateway and can be removed from the service-tier design.
- 27 open-source tools that can make your Kubernetes workflow easier 🚀🥳
-
Difference between Reverse Proxy, Load Balancer and API Gateway
I am seeing different companies taking different approach. I am not sure anymore where each should be actually used. On top of that tech like Kong make me question whether API Gateway should be one thing for all. Some perspective into this would be really appreciated.
What are some alternatives?
mirotalk - 🚀 WebRTC - P2P - Simple, Secure, Fast Real-Time Video Conferences Up to 4k and 60fps, compatible with all browsers and platforms.
apisix - The Cloud-Native API Gateway
KrakenD - Ultra performant API Gateway with middlewares. A project hosted at The Linux Foundation
Jitsi Meet - Jitsi Meet - Secure, Simple and Scalable Video Conferences that you use as a standalone app or embed in your web application.
Hasura - Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
jitsi-meet-electron - Jitsi Meet desktop application powered by :electron:
konga - More than just another GUI to Kong Admin API
ms-teams-rce
Keycloak - Open Source Identity and Access Management For Modern Applications and Services
jami-cli - Jami client for terminal
kubernetes-ingress-controller - :gorilla: Kong for Kubernetes: The official Ingress Controller for Kubernetes.