admin/felhom-controller
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: CHANGELOG v0.113.0 + REPORT + CONTEXT + README NAS section + REUSE seams

Browse Source 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PSK5g6qYLknKj8u3QAFEr6
This commit is contained in:
authentik Default Admin
2026-07-11 10:31:07 +02:00
parent a65dcff85a
commit 5d06ecf374
5 changed files with 186 additions and 58 deletions
Download Patch File Download Diff File Expand all files Collapse all files
controller/README.md
+15
View File
@@ -798,6 +798,21 @@ not just those with HDD data. Non-HDD apps can configure destination, method, an
> path server-side (`refuseNetworkLifecycle`). The **drive-absent gate** (`planDriveGates`) and the
> **missing-storage** surface **skip network paths**, so an `unreachable` NAS is a **recoverable warning**
> (`networkStorageWarnings` → a distinct app-card badge), **never** the drive "missing → stopped" cascade.
> - **Verify-before-commit (v0.113.0, pairs with agent v0.81.0; SPIKE-nas-verify-2026-07-11):** add no
> longer registers blind. `POST /api/storage/netstorage/add` returns `{started:true}` and a DETACHED
> single-flight orchestration job (`internal/web/netstorage_job.go`, migrate.go shape; polled on
> `GET /api/storage/netstorage/add/status`) drives `agent_add → verifying → probing → registering`:
> the agent installs the units + runs its own detached mount-verify (journal-classified, agent-side
> auto-rollback), then the controller re-execs itself as **`--netprobe <dir>` at uid/gid 1000**
> (`SysProcAttr.Credential`, `netprobe*.go`) to prove a media app can WRITE through the share (the
> squash trap), and only then registers. ANY failure = full rollback (nothing registered, nothing
> installed, no creds file); categorized Hungarian errors (`netAddMessage`, §3.2 map — note
> `nfs_export` merges not-found/not-permitted: NFSv4 returns identical strings). An agent restart
> mid-verify (`verify-status` phase `none`) ⇒ controller rollback; any agent-configured share NOT in
> the registry surfaces as a remove-only **"Árva megosztás"** orphan row. The page
> (`storage_network.html`) is on the canonical form pattern with staged poll progress and the
> protocol-honest NAS guidance (SMB-first; NFS map-all-users vs full-fidelity `anonuid=<uid+100000>`).
> Authoritative doc: `felhom.eu/documentation/controller/network-storage-nas.md`.
> - **Limits (v1):** a share's `+100000` uid mapping is fixed at add-time (one app / same-uid apps); for
> write apps on a soft NFS mount, an in-flight file can truncate if the NAS vanishes mid-write (prefer
> atomic-write apps / SSD-staging).