@vy it's still a bit oof'd and not automated, but I have js code that gets all the configurations from the database and turns it into a working Nix config!

https://git.pixie.town/f0x/waasig/commit/b9a57eec46fe53097011e9769df680dee99b9365

which in turn generates container definitions with the required wireguard network(s) and peers

@f0x ooooh, nice!

I don’t understand the workflow or how it starts, but I appreciate the challenge!

@vy basically the idea is to have a friendly webinterface for end-users where they can click together their networks, and download a pre-configured wireguard config for their raspberry pi etc.

The backend will then take all this configuration and apply it to the NixOS system that runs it all, spinning up containers for each user, and within those containers setting up the various wireguard network interfaces with peers as neccessary

with the endgoal of having easy NAT punching (and next up: reverse proxying on (sub)domains too) for users who don't want to bother maintaining their own central rendezous server

@vy and also where my nosql comment came from lol, because I have to get *all* containers/networks/peers rows anyways and I couldn't wrap my head around the sql querying well enough so just doing all the nesting in js was easier haha