tealsql VS dispatch-proxy

A project that uses tealr can be found at https://github.com/lenscas/tealsql/tree/master/pgteal, with online documentation available over at https://lenscas.github.io/tealsql/

There is also https://github.com/lenscas/tealsql which is used as kind of showcase project for tealr and tealr_doc_gen. While at the same time (hopefully) filling a pain point in the lua/teal eco system.

tealsql, my sql library for lua: Right now, it is being used to dog feed the changes in tealr. So, mostly improving its documentation, and preparing it to release it.

last weekend I put in some more time in tealsql, a postgresql client written in Rust for lua/teal.

The main focus is my sql client for teal/lua https://github.com/lenscas/tealsql , mainly getting rid of every part in the api that doesn't have a good type yet on the teal side of things (any, {any:any}, etc.

tealsql, an sql client for teal/lua. Current plan is to get the async api finished (right now it ignores every error but otherwise works without problems).

Since I cannot setup the LAG on the black box modem, nor am confident for it to have that feature, I was wondering if OPNsense could just pull several streams across several medias, for example I know that piece of software which pulls both from ethernet and wifi, to increase the throughput : https://github.com/alexkirsz/dispatch-proxy

is there some feature to toggle in this OS that reproduces the behavior of https://github.com/alexkirsz/dispatch-proxy ?

But nothing like that https://github.com/alexkirsz/dispatch-proxy

Working on getting a first stable release of dispatch out. It's a Rust rewrite of a small CLI utility I wrote in CoffeeScript(!) 8 years ago(!!), which allows you to combine multiple internet connections into one (among other things!).