History

ZDDC 70591dcfa6 feat(server,browse): .zddc.zip bundle visible+editable to standing config-editors The config bundle followed the old elevation gate: only an elevated admin could browse or edit it. Bring it in line with the standing config-edit model — a subtree admin / `a`-verb holder over the bundle's directory may browse AND edit it without toggling. Elevation stays purely additive. activeAdminForBundle → configEditorForBundle (zddc.IsConfigEditor, no Elevated). Gates both the existence-hiding visibility check and the ServeZipWrite path. Deliberately scoped to config-EDITORS, not all readers: one .zddc.zip packs many subtrees' policy into a single file, so wide read would leak a tightened subtree's rules — per-level transparency is served by ServeZddcFile (already read-ACL'd) instead. Client: isEditableZipMember drops the isElevated() check — the server gates bundle visibility on config-edit authority, so if a member is visible the session can edit it. Tests: TestDispatchBundleAdminView now expects an un-elevated admin to SEE the bundle (non-editor reader still 404); TestDispatchBundleAdminWrite adds an un-elevated config-editor write. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>		2026-06-05 17:05:34 -05:00
..
css	feat(browse): drop New folder/file toolbar buttons, lift Sort/Hidden above filter	2026-06-05 16:03:25 -05:00
js	feat(server,browse): .zddc.zip bundle visible+editable to standing config-editors	2026-06-05 17:05:34 -05:00
build.sh	feat(browse): schema-driven .zddc form view (option fields editable, structure read-only)	2026-06-05 15:02:47 -05:00
README.md	feat(browse): generic directory listing tool — default at folder URLs	2026-05-03 19:56:51 -05:00
template.html	feat(browse): drop New folder/file toolbar buttons, lift Sort/Hidden above filter	2026-06-05 16:03:25 -05:00

README.md

browse — directory listing tool

Generic file browser for any directory. Designed to work with ZDDC archives but useful for any folder. Single-file HTML, no install.

How it's used

Two modes, auto-detected at page load:

Online (zddc-server backed). When this HTML is served by zddc-server at a folder URL — which it is by default for any directory under ZDDC_ROOT that doesn't have an index.html — the JS queries the same URL with Accept: application/json to load the directory's listing and renders it as a sortable, filterable table.
Local (FileSystemAccessAPI). Click "Select Directory" in the header to pick any folder on your computer. Works in Chromium-based browsers (Chrome, Edge, Brave, etc.). No server required; the directory is read directly from disk.

What it does

Lists files and folders with name, size, type (extension), and modified date.
Click a folder to expand inline. Children load lazily on first expand.
Click a column header to sort by that column. Click again to reverse.
Type in the filter to narrow to entries whose name contains the substring.
Click any file to open it in a new tab — for server-backed pages, this routes through zddc-server's normal handler (so an .archive redirect, an apps cascade override, etc. all work as expected).

Design notes

No ZDDC-specific filtering. This tool is intentionally domain-agnostic. The companion archive tool layers ZDDC parsing (project / status / revision filters, tracking-number resolution) on top of the same listing API. Use archive when you want ZDDC semantics; use browse when you just want to see what's in a folder.
Default at directory URLs. zddc-server's directory.go serves the embedded browse.html bytes for any directory request with Accept: text/html and no index.html present. This means a user navigating to any folder under ZDDC_ROOT gets a usable browser without anyone having to drop a file into the archive.
Apps cascade override. Like every other ZDDC tool, the served browse.html can be overridden per-folder via a .zddc apps: entry. The default is the embedded copy from the binary; operators can pin a specific version or URL if they want.