Dawnline 0.20.0
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 / Backend (Go: vet, tests, a real ubusd and uhttpd) (push) Blocked by required conditions
CI / Package files (push) Blocked by required conditions

- **Backend rewritten in Go.** One daemon, `dawnlined`, replaces the whole ucode backend: the rpcd plugin, the agent, the CLI and the updater. The package no longer depends on ucode.
- **Per-architecture builds.** The release carries the backend for arm64, ARMv7, mips, mipsle and amd64; the router fetches its own after the package is installed and checks its sha256. Dawnline does not run on other architectures (older ARM, 32-bit x86, RISC-V).
- **Faster on the router.** A firewall sync takes 0.06 s instead of 0.9 s; a full apply takes about 300 ms. The portal is served by the daemon itself, without a CGI process per request.
- **Live pages.** The admin and the portal follow a live stream from the router instead of re-fetching the whole state every 30 seconds.
- **Admin redesigned in the portal's style.** Three sections (Overview · Log · Settings); a server is a page of its own with People, Places and Settings; a device opens as a dialog over its person.
- **Changes wait for «Apply».** Every setting, and a person's access, is staged in one dock before it reaches the router.
- **Configuration rollout.** After a change that makes devices fetch their configuration again, the admin shows how many have fetched it and who has not. Every setting shows beforehand (⟳N) how many devices it will touch.
- **Waiting for a decision.** Overview and People put first the people who need one (access ended, limit reached, a device that does not connect), each with its one action a tap away.
- **Bulk actions on people.** «Select» (or a long press on a card) picks several people to extend by a month, pause or resume at once.
- **Undo.** An action done from a card or a request is undone from its toast.
- **Update dialogs redesigned.** An update is one view from its question to its result; Dawnline's own update runs in it like every other, and the page reloads itself once the new version answers. Other versions are a list, each with its notes and Install on a page of its own.
- **Site to site: networks behind a router.** A router connected as a device can have networks behind it (up to eight, /16 to /30): the server routes them and applies the router's access to them. A network that shares addresses with a tunnel, the router's own networks or another site is refused by name.
- **Routers from the portal.** People can add a router and name its networks on their own page; the admin accepts or declines with a reason, or lets them through without asking.
- **Check access and Health know the networks behind routers.**
- **Usage limits reworked.** A monthly limit no longer follows the calendar. A person's month starts with their first traffic and ends a month later; the next one starts only when they connect again, so time away uses up none of it. Before, everyone's limit reset on the 1st.
- Extra data lasts until that person's month ends; «Reset usage» starts the month anew.
- A limit is for a month or for the whole term; the admin and the portal show when it resets.
- Charts that said «this month» show the last 30 days.
- After the update nobody loses what was counted: the month that was running becomes the person's first and ends on the 1st.
- **Access by time of day removed.** The Hours limit is gone from the admin, the portal and the backend; saved hours are dropped.
- **Expiry simplified.** An end date always stops access, with a heads-up three days before; the per-person choice is gone.
- **No false disconnects from sleeping phones.** A phone or a tablet stays online through ten minutes of silence.
- **Mobile Safari fixes.** Pressing a control no longer sends the page to its top; tab tracks that do not fit scroll; switches animate after a press.
This commit is contained in:
Aemeath committed 2026-11-13 09:43:50 +03:00
1 parent f8130e39a8
commit ac90575b0b
788 files changed
+139244 -41720

No files matched your search

+142
View File
@@ -0,0 +1,142 @@
// The ucode backend's `status` answer cut into the topics pages follow.
//
// `status` is one large document that every admin page used to fetch whole.
// As topics, a change in one place (a device came online) is a patch of a few
// bytes to one of them, and a page follows only those it shows. Lists of
// things that have an id (people, devices, servers) become keyed lists, so a
// change to one entry does not resend the list.
//
// Pure: a document in, documents out. bridge.go fetches and publishes.
package bridge
// A keyed list is how a list of things with ids is published:
//
// { "order": ["p1", "p2"], "items": { "p1": {…}, "p2": {…} } }
//
// A merge patch replaces an array whole, but reaches into an object: with
// the entries under their ids, one that changed is all that is sent, and
// `order` only when something came, went or moved. A daily series (traffic
// by the day) is keyed by its `day` the same way: every minute moves today's
// entry, and on the router that alone was most of what a refresh resent.
func keyed(list []any) (map[string]any, bool) {
for _, key := range []string{"id", "day"} {
if k, ok := keyedBy(list, key); ok {
return k, true
}
}
return nil, false
}
// keyedBy keys a list by one field, when every entry has it, as a string of
// its own.
func keyedBy(list []any, key string) (map[string]any, bool) {
order := make([]any, 0, len(list))
items := make(map[string]any, len(list))
for _, e := range list {
m, ok := e.(map[string]any)
if !ok {
return nil, false
}
id, ok := m[key].(string)
if !ok || id == "" {
return nil, false
}
if _, twice := items[id]; twice {
return nil, false
}
order = append(order, id)
items[id] = m
}
return map[string]any{"order": order, "items": items}, true
}
// Null stands for a null of the ucode answer: a topic holds none (a merge patch reads null as "remove this"),
// and the pages' code tells "no link trouble" (null) from "not told" (absent). A field that was null is
// published as { "$null": true } and read back as null (web/src/admin/state/join.ts). Only this bridge
// needs it: a producer written for the stream leaves out what it has nothing to say about.
const Null = "$null"
// rekey turns every list of things with ids (or days) inside v into a keyed
// list, at any depth (a person's devices inside the list of people). A list of
// anything else stays a list. An empty list stays one too: it cannot be told
// what it would hold.
func rekey(v any) any {
switch x := v.(type) {
case nil:
return map[string]any{Null: true}
case map[string]any:
for k, e := range x {
x[k] = rekey(e)
}
case []any:
for i, e := range x {
x[i] = rekey(e)
}
if len(x) > 0 {
if k, ok := keyed(x); ok {
return k
}
}
}
return v
}
// Where each field of `status` goes. A field not named here goes to "router",
// so one a later version adds is still published.
var topicOf = map[string]string{
"servers": "servers",
"people": "people",
"circles": "circles",
"services": "services",
"totals": "traffic",
"series": "traffic",
"hours": "traffic",
"geo": "places",
"events": "recent",
"now": "clock",
"tz": "clock",
}
// Topics lists the topics Split fills, for hello and the tests.
var Topics = []string{"router", "servers", "people", "circles", "services", "traffic", "places", "recent", "clock"}
// whole names the topics that are one field of `status` as it is; the others
// are objects of several fields.
var whole = map[string]bool{"servers": true, "people": true, "circles": true, "services": true, "places": true, "recent": true}
// lists names the topics that are a keyed list even while empty, so a page
// reads one shape whether or not there is anyone yet.
var lists = map[string]bool{"servers": true, "people": true, "circles": true, "services": true}
// Split cuts a `status` answer into topics. The answer is taken apart, not
// copied: the caller gives it up.
func Split(status map[string]any) map[string]any {
out := map[string]any{}
for _, t := range Topics {
if !whole[t] {
out[t] = map[string]any{}
}
}
for field, v := range status {
topic, ok := topicOf[field]
if !ok {
topic = "router"
}
if whole[topic] {
// The recent events have no ids and come as a window that moves:
// they stay a list.
if topic != "recent" {
v = rekey(v)
}
if list, isList := v.([]any); isList && lists[topic] {
if k, ok := keyed(list); ok {
v = k
}
}
out[topic] = v
continue
}
out[topic].(map[string]any)[field] = rekey(v)
}
return out
}