apisix VS docker-jitsi-meet

Through this intelligent caching mechanism, APISIX efficiently utilizes system resources when handling a large volume of requests, thereby improving overall system performance and stability. APISIX, with its advanced LRU cache, provides developers with a reliable and efficient API gateway solution, facilitating smooth communication with external services.

The main issue is that priority is documented in the config-default.yaml file, while the phase is buried in the code. Worse, some plugins run across different phases. For example, let's check the proxy proxy-rewrite plugin and, more precisely, the functions defined there:

// references: // https://github.com/tetratelabs/proxy-wasm-go-sdk/tree/main/examples // https://github.com/apache/apisix/blob/master/t/wasm/ package main import ( "github.com/tetratelabs/proxy-wasm-go-sdk/proxywasm" "github.com/tetratelabs/proxy-wasm-go-sdk/proxywasm/types" "github.com/valyala/fastjson" ) func main() { proxywasm.SetVMContext(&vmContext{}) } // each plugin has its own VMContext. // it is responsible for creating multiple PluginContexts for each route. type vmContext struct { types.DefaultVMContext } // each route has its own PluginContext. // it corresponds to one instance of the plugin. func (*vmContext) NewPluginContext(contextID uint32) types.PluginContext { return &pluginContext{} } type header struct { Name string Value string } type pluginContext struct { types.DefaultPluginContext Headers []header } func (ctx *pluginContext) OnPluginStart(pluginConfigurationSize int) types.OnPluginStartStatus { data, err := proxywasm.GetPluginConfiguration() if err != nil { proxywasm.LogErrorf("error reading plugin configuration: %v", err) return types.OnPluginStartStatusFailed } var p fastjson.Parser v, err := p.ParseBytes(data) if err != nil { proxywasm.LogErrorf("error decoding plugin configuration: %v", err) return types.OnPluginStartStatusFailed } headers := v.GetArray("headers") ctx.Headers = make([]header, len(headers)) for i, hdr := range headers { ctx.Headers[i] = header{ Name: string(hdr.GetStringBytes("name")), Value: string(hdr.GetStringBytes("value")), } } return types.OnPluginStartStatusOK } // each HTTP request to a route has its own HTTPContext func (ctx *pluginContext) NewHttpContext(contextID uint32) types.HttpContext { return &httpContext{parent: ctx} } type httpContext struct { types.DefaultHttpContext parent *pluginContext } func (ctx *httpContext) OnHttpResponseHeaders(numHeaders int, endOfStream bool) types.Action { plugin := ctx.parent for _, hdr := range plugin.Headers { proxywasm.ReplaceHttpResponseHeader(hdr.Name, hdr.Value) } return types.ActionContinue }

API7 takes Apache APISIX as its robust foundation, which is open-source and has an active community with over 600 contributors all over the world. The nature of open source allows users to examine the source code, which promotes transparency. This transparency helps users understand how APISIX works, verify its security, and identify and fix any potential vulnerabilities or bugs.

But the best part is that the libraries mentioned here and Apache APISIX are entirely open source, meaning you can look under the hood and modify things yourself.

Default configuration

4. Plugin definition: It is a really important part of plugin implementation that we define as a table with properties for the version, priority, name, and schema. The name and schema are the plugin's name and schema defined earlier. The version and priority are used by APISIX to manage the plugin. The version typically refers to the version that is currently in use like API versioning. If you publish and update your plugin logic, it is going to be 1.1 (You can set any version you wish). But you need to be very careful in choosing priority. The priority field defines in which order and phase your plugin should be executed. For example, the 'ip-restriction' plugin, with a priority of 3000, will be executed before the 'example-plugin', which has a priority of 0. This is due to the higher priority value of the 'ip-restriction' plugin. If you're developing your own plugin, make sure that you followed the order of plugins not to mess up the order of existing plugins. You can check the order of existing plugins in the config-default.yaml file and open the Apache APISIX Plugin Development Guide to determine.

Their use of etcd was a hard pass for me; I don't need more etcd in my life

Apache APISIX Apache APISIX is an open source, dynamic, real-time, high-performance cloud native API gateway. APISIX provides rich traffic management features such as load balancing, dynamic upstream, canary release, circuit breaking, authentication, observability, and more. Official website https://apisix.apache.org/ GitHub projects APISIX (the core): https://github.com/apache/apisix GitHub - apache/apisix: The Cloud-Native API Gateway GitHub - apache/apisix-dashboard: Dashboard for Apache APISIX GitHub - apache/apisix-website: Apache APISIX Website GitHub - apache/apisix-docker: the docker for Apache APISIX GitHub - apache/apisix-go-plugin-runner: Go Plugin Runner for APISIX GitHub - apache/apisix-java-plugin-runner: APISIX Plugin Runner in Java GitHub - apache/apisix-python-plugin-runner: Apache APISIX Python plugin runner GitHub - apache/apisix-helm-chart: Apache APISIX Helm Chart GitHub - apache/apisix-ingress-controller: ingress controller for K8s

Grafana configuration. Most of it comes from the configuration provided by APISIX.

Jitsi Meet for selfhosted Video Meetings

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

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.

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.

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.

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?

download the latest release from https://github.com/jitsi/docker-jitsi-meet/releases (at time of writing stable-6173: release)

+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.

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.