rustify VS tealsql

Just recently released a pretty decent overhaul of rustify that increases its ability to scaffold various HTTP APIs. It's nearing a 1.0 release as I don't see the feature-set needing to grow any past this point. It's been powering vaultrs for a while now and has really streamlined the process of scaffolding dozens of endpoints (probably close to a 100 in that crate alone).

I'm a relative newcomer to Rust and this is the second crate I've produced since starting to learn it a few weeks ago. It relies heavily on my first crate for defining the architecture of the Vault API.

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