Dawnline 0.4.0
Build packages / Version (push) Waiting to run

- Components tab replaces Updates: Dawnline, the AmneziaWG build for this
  firmware (Slava-Shchipunov 2.0 or 2Grey 3.1, Russian translation) and
  the system packages Dawnline adds, each checked, installed, reinstalled
  or rolled back in place, with What's new, versions and an activity log
- Automatic updates: daily check, install at a set time or right away,
  per component; AmneziaWG is left out by default and an automatic run
  never switches its build or generation
- Downloads verified against GitHub's sha256; mirrors are used only when
  GitHub is unreachable and the hash is known
- New installer: checks firmware, clock, space and DNS, lets you pick a
  release, shows the plan and asks first; --dry-run
- New uninstaller removes everything Dawnline added (cron, nft, firewall,
  routing, interfaces, packages it installed); --dry-run
- Works without AmneziaWG on the router: Overview, the setup wizard,
  Health and Components say what is missing and offer to install it
- Overview shows failed health checks as notices with their fix
- People list no longer reads the config from the browser: private keys
  stay on the router; personal links are fetched on demand
- Config changes are serialized under one lock, the nft table loads
  atomically and fails closed, and Dawnline never touches network
  sections it did not create
- The portal never opens system ports, keeps disabled devices disabled,
  rate-limits per address and counts days by the router's clock
- Settings and Diagnostics load their heavy parts in the background
- Release notes are written from the commits since the previous release
- Backend and admin UI split into small single-purpose modules
This commit is contained in:
Aemeath committed 2026-10-16 02:14:15 +03:00
1 parent 70a932b8ea
commit 34293fb8e5
158 files changed
+17418 -10022

No files matched your search

+41
View File
@@ -0,0 +1,41 @@
// What every tunnel core gives the admin (cores/index.ts holds the registry),
// what a core's settings card gets from the Server page, and that card's head.
import type { ClientConfig, Server, Status } from '../../shared/types';
import { E } from '../e';
/** What the Server page hands a core's settings card. */
export interface CoreCtx {
st: Status;
/** server_update with these values, then refresh. */
save: (values: Record<string, unknown>, ok?: string) => Promise<void>;
refresh: () => Promise<void>;
}
/** A tunnel core (AmneziaWG today): its name and the pieces of the admin that differ per core. */
export interface Core {
id: string;
/** "AmneziaWG": the server section, the address bar, the settings card. */
label: string;
/** Server → <label>: the core's own settings. */
settingsCard(ctx: CoreCtx, srv: Server): HTMLElement;
/** Overview: how the tunnel looks on the wire (the disguise tile). */
overviewTile(srv: Server): HTMLElement;
/** How a device connects: file / key / QR. */
connectBlock(cfg: ClientConfig, initial?: 'file' | 'key' | 'qr'): Promise<HTMLElement>;
/** What a QR code for the device carries. */
qrText(cfg: ClientConfig): string;
/** The key the device's app imports (⋯ → Copy key), with the menu label. */
appKey?: { label: string; make(cfg: ClientConfig): Promise<string> };
/** The config file the device imports, with the menu label. */
file: { label: string; make(cfg: ClientConfig): { name: string; text: string } };
}
/** Name, state pill and a short line: the head of a core's settings card. */
export function coreHead(title: string, tone: 'ok' | 'bad' | 'off' | '', state: string, sub: string): HTMLElement {
return E('div', { class: 'dl-corehead' }, [
E('h3', {}, title),
E('span', { class: `dl-pill ${tone}` }, state),
sub ? E('span', { class: 'dl-sub' }, sub) : '',
]);
}