Build packages / CI (push) Blocked by required conditions
Build packages / Version (push) Waiting to run
CI / Web (format, types, tests, bundles) (push) Blocked by required conditions
CI / ShellCheck (push) Blocked by required conditions
CI / ucode static checks (push) Blocked by required conditions
CI / ucode compiles and tests pass (OpenWrt 24.10) (push) Blocked by required conditions
CI / ucode compiles and tests pass (OpenWrt 25.12) (push) Blocked by required conditions
- Russian translation. The admin pages, the LuCI menu and the router's messages (errors, Health checks, update steps, the service log) come in Russian with the new luci-i18n-dawnline-ru package, released beside the app. LuCI shows it when its language is Russian, or "auto" with a Russian browser - The translation installs with install.sh when LuCI is in Russian (or with --lang ru), follows every Dawnline update and rollback, and can be added or removed in Components → Dawnline → Translation - The portal speaks the visitor's language: it opens in the system's language and switches between English and Russian in place, from the language pill beside its QR code. It carries its own translation and needs no package - Set-up steps quote the apps' own menus word for word, in Russian too: AmneziaVPN is "+ → Insert → Continue" (it has no "Add server"), and the Mac and Windows menus of WireGuard and AmneziaWG have their real names - Questions in the portal (Reconnect, Remove) read from the left edge and close with Cancel, without × - Numbers, sizes and dates follow the page's language. A server that can't start says why in one sentence; event details and service log lines read as whole sentences - README in Russian (README_ru.md). rules/i18n.md: how strings are written and translated; CI checks the catalogs (npm run i18n:check)
3.4 KiB
3.4 KiB
Backend (ucode on the router)
Read with code-standards.md. Everything here runs on a small router (2 × Cortex-A53 on the reference Cudy WR3000P): cost is part of correctness.
Layers
util,schema(validation) →core(model, allocation) →store(the only writer of/etc/config/dawnline) → domain modules (net,nft,fw,netifd,awg,loop,resolver,live,health,backup, …) →apply(reconciliation) → entry points (rpc/*,portal, thedawnlineCLI, the agent, the updater).- Read models for the UI live in
view; RPC modules translate arguments and call down, they hold no business logic. - The updater is a thin dispatcher over
upd_app/upd_awg/upd_pkgs, with GitHub ingithub, the package manager inpkg, policy/locks/history inupdates. - Live state: the agent's watcher owns who is online (
live.PRESENCE); readers asklive.online(), never re-derive it from handshake ages. Online means the WireGuard session lives (live.ONLINE_WINDOW): traffic silence is no signal, a phone asleep is silent too.
ucode
'use strict'in entry points; modulesimport { … } from 'fs'/'dawnline.x'. Subdirectories map to dots (dawnline.rpc.status→dawnline/rpc/status.uc).- Exported functions end with
};(the compiler requires it). No destructuring. Regexes are POSIX (no(?:),\s\Sclasses, lazy quantifiers); anchor them. - Modules with
exportcannot be loaded withrequire(): imports are static and compiled on every start of the script. - Doc comments (
/** … */) on every export: what it returns, including the null/empty case. - Shell out through one small helper per module (
run()/sh()), with2>&1captured and the exit code checked. - Messages people read (
die()texts, check titles and details, phases) go through_()/N_()ofdawnline.i18n, inside functions, withsprintf()for values (i18n.md). - nft changes load as one script (
nft.load(), a transaction); tables Dawnline owns are nameddawnline*and rebuilt whole (table X+delete table X+ the table).
Cost on the router
- The portal is CGI: every request starts ucode and compiles the module graph, about 140 ms of CPU before any work (a full
stateanswer about 180 ms). No periodic polling from the portal; one request per user action. - rpcd keeps the admin backend loaded: LuCI RPC calls are cheap, so the admin UI may poll small methods often (
rev), and the heavy ones (status) only on change or rarely. - Code on the agent's 1-second watcher stays in the low milliseconds: one
awg show all dump(about 4 ms with process start), the model cached by the config file's mtime/inode (core.load()is about 4 ms), files written only when something changed. Slow work (geo lookups, apply) runs only on a transition. - Measure before and after on the router (a loop of 20–200 calls,
/proc/self/statCPU ticks, system busy from/proc/stat) when adding anything periodic.
Checks
scripts/lint-ucode.pyandscripts/ucode-container.sh(compiles and runstests/ucodein the OpenWrt rootfs containers;scripts/check-ucode.shcompiles on the router instead) pass before any deploy; new directories and entry points are added tolint-ucode.pyandscripts/compile-ucode.sh, and executables to the mode check in.github/workflows/ci.yml.- Pure functions get a case in
tests/ucode/<module>.test.uc; what reads the clock takes an optionaltsso a test can pass one.