From e7678e3c4d4911abffc5a3759c529cdc27d95e73 Mon Sep 17 00:00:00 2001 From: ZDDC Date: Thu, 7 May 2026 10:05:59 -0500 Subject: [PATCH] =?UTF-8?q?docs(index):=20order=20zddc-server=20bullets=20?= =?UTF-8?q?general=20=E2=86=92=20specific;=20simplify=20run?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Re-sort the zddc-server feature list so the most-immediately-useful behaviours (lazy folder creation, virtual .archive URLs, basic ACL, roles, WORM, cascade tracer) come first, then the operational table stakes (per-request logging, TLS hygiene), and the federal/regulated bullets (OPA decider, designed-for-regulated-environments) last. Within each tier the simpler item leads. Strip the explicit ZDDC_ROOT=/srv/zddc from the run example. The binary defaults to the current working directory, so for a quick start "./zddc-server" is all that's needed. Add a follow-on note that the listener defaults to https://localhost:8443/ with a self-signed cert and that --root / --addr / --tls-* override the defaults. Co-Authored-By: Claude Opus 4.7 (1M context) --- index.html | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/index.html b/index.html index ebabf23..1f1c8fa 100644 --- a/index.html +++ b/index.html @@ -175,6 +175,8 @@

zddc-server is a small Go binary purpose-built to serve ZDDC archives. Any web server gives you online mode; zddc-server adds things a generic web server can't:

The on-disk layout is the same in both modes. Stop the server and the directory is still a perfectly valid ZDDC archive that opens in local-directory mode. The server is convenience, not lock-in.

@@ -207,7 +207,7 @@ Role definitions cascade like everything else; a child .zdd

Server: just run zddc-server

-

The binary has the current-stable build of all five tools baked in at compile time. They appear automatically at the right paths under ZDDC_ROOT:

+

The binary has the current-stable build of all five tools baked in at compile time. They appear automatically at the right paths in the served tree:

  • archive.html and browse.html at every level (root, project, archive, party)
  • mdedit.html in any working/ directory and its subtree
    • @@ -217,7 +217,8 @@ Role definitions cascade like everything else; a child .zdd
  • index.html (the project picker) at the deployment root

Folder names are case-insensitive — Working/, working/, and WORKING/ all match the working/ rule.

-
ZDDC_ROOT=/srv/zddc ./zddc-server
+
./zddc-server
+

No flags needed for a quick start. The served tree defaults to the current working directory; the listener defaults to https://localhost:8443/ with a self-signed certificate. --root, --addr, and --tls-cert / --tls-key override each. --help prints the full flag list.

To override a tool at any path: drop a real .html file there — that file wins over the baked-in version. To pin a different version, write an apps: entry in any .zddc file along the path:

# <project>/.zddc
 apps: