yaps | Yet Another Provisioning System - simple

Simply clone respective repository, npm install frontend dependencies and start / tell your webserver about the document root and cgi-bin directory. For uhttpd - the default webserver used by OpenWrt - a command line would look like this: uhttpd -f -p 0.0.0.0:8080 -h /yaps.git -r YAPS -x /cgi -t 60 -T 30 -k 20 -A 1 -n 1 -N 10 -R.
An idea is that the hardware running YAPS is a small embedded device, featuring USB ports and - depending on the type of to be provisioned client devices - ethernet. That's where the "runs on OpenWrt"-feature originates from - a cheap WiFi-router (with disabled WiFi) works perfectly fine as underlying hardware. As quite some IoT devices don't feature ethernet connectivity anymore (but only WiFi - and WiFi is a notoriously bad idea to use for transporting initial, precious and confidential provisioning information to a device) I came up with using PPPoS (PPP over Serial/UART). In practice that means, that I provision my ESP8266 development board via YAPS over HTTP over IP over UART over USB. Well, it does the job. Following up on the general idea, the actual provisioning data is stored on external media, let's say USB thumb drives - not on the system running YAPS itself. Each such drive is dedicated to a particular infrastructure/project. That way, depending for which infrastructure/project you'd want to provision clients, you'd just insert/swap respective drives. Also batches of (additional) provisioning sets should be stored and imported via external media, dedicated for the sole purpose of importing batches. Same goes for backups.