How ffbs/gluon-parker works
Project type and purpose
• Gluon-Parker is a firmware-build framework: it is neither a traditional web app nor a microservice suite but a collection of build scripts, Makefiles, packages, patches, and CI workflows that produce preconfigured OpenWrt images for mesh-network routers.
• Its purpose is to ingest upstream OpenWrt, apply Gluon framework packages and Parker-specific patches, and output ready-to-flash firmware for multiple hardware targets.
File structure
• Top-level “Makefile”, “scripts/”, “package/”, “patches/”, “targets/”, “.github/workflows/” and “contrib/” directories reveal a build-pipeline architecture.
• “package/” contains dozens of Gluon modules (Lua/C files, init scripts, upgrade hooks) that implement mesh protocols, web UI, autoupdater, VPN, etc.
• “scripts/” holds build orchestration helpers (feed management, image customization, manifest generation).
• “targets/” enumerates supported hardware target definitions.
• “patches/” holds OpenWrt and package patches.
• “.github/workflows/” defines CI pipelines: build-container, lint, check-ci, build-docs, backport, etc.
README for additional insights
• The README confirms the forked Gluon framework, Parker-style routing extension, community-package integration, and CI-driven branching strategy.