ZDDC
d37ff58e11
bootstrap/install.sh is a POSIX-sh script that handles all three ZDDC deployment patterns plus both target shapes in a single command. The homepage's "Install on your server" section now prints `sh -c "$(curl -fsSL https://zddc.varasys.io/install.sh)"` invocations instead of inlining four separate cURL loops. Modes / channels / target: --mode copy (default) fetch actual HTML files locally; site is self-contained after install. --mode track install level-2 stubs that fetch the channel from upstream on every page load. Only valid with channel names (stable/beta/alpha); for pinned versions, use --mode copy. --channel stable (default) --channel beta | alpha channel mirrors (auto-update upstream) --channel 0.0.2 exact version --channel 0.0 latest patch within 0.0.x (symlink-resolved) --channel 0 latest within 0.x (symlink-resolved) Optional leading 'v' is accepted. --target root 5 tool HTMLs (incl. landing as index.html) plus _template/ directory of level-1 stubs --target project 4 level-1 stubs that fetch ../<tool>.html --target auto (default) detect from CWD: 'project' if parent has a ZDDC-looking index.html, 'root' otherwise --source URL Override the upstream base URL (default: https://zddc.varasys.io). Use this to point at a private dev server during alpha work; install.sh sed-rewrites the embedded source inside fetched track-channel stubs so they use your URL. Also: - website/index.html — replaces the four inlined install-card snippets with four use-case-oriented cards that all invoke the same script (self-contained / track-channel / pin-to-version / project-subdir). - website/index.html — fixes the stale "pre-built image at codeberg.org/ varasys/zddc-server (channel-tagged :stable, :beta, :alpha)" reference; zddc-server is now distributed as Codeberg release-asset binaries with helm chart examples in the repo. - website/install.sh — symlink to ../bootstrap/install.sh so the upstream serves the script at https://zddc.varasys.io/install.sh. Verified end-to-end against a file:// source: copy:root, copy:project, track:root with custom --source (rewrite of base URL inside fetched stub), and auto-detection of project vs root from CWD's parent index.html all behave correctly. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| archive | ||
| bootstrap | ||
| classifier | ||
| landing | ||
| mdedit | ||
| pandoc | ||
| shared | ||
| tests | ||
| transmittal | ||
| website | ||
| zddc | ||
| .gitignore | ||
| AGENTS.md | ||
| ARCHITECTURE.md | ||
| build.sh | ||
| CLAUDE.md | ||
| dev-server | ||
| freshen-channel | ||
| LICENSE.txt | ||
| package.json | ||
| playwright.config.js | ||
| README.md | ||
Zero Day Document Control (ZDDC)
The Universal Distributed Filing Cabinet
ZDDC is an information management convention plus a small set of single-file HTML tools. Every deliverable's filename encodes its tracking number, revision, status, and title; every transmittal folder is date-prefixed and self-describing. A plain shared folder becomes a fully searchable, auditable archive — no server, no database, no software required to read it.
The name "Zero Day Document Control" comes from the convention itself — adopt it on day zero of a project, with no setup time. The tools are optional interfaces around the structure; the structure works without them.
For end users: https://zddc.varasys.io/ introduces the project, links to all tool channels (stable / beta / alpha), and prints copy-paste shell snippets to install on a self-hosted deployment.
Tools
| Tool | What it does |
|---|---|
| Archive Browser | Browse, search, and filter a project archive folder. Group by transmittal, export selections as ZIP. |
| Transmittal Creator | Self-contained HTML transmittal records with SHA-256 checksums and optional digital signatures. |
| Document Classifier | Spreadsheet-like bulk-renamer that copy/pastes with Excel and writes back to disk. |
| Markdown Editor | Browser-based markdown editor with YAML front matter, TOC, and direct local file access. |
Each tool is published in three channels (stable, beta, alpha) as Codeberg release assets, browsable at https://zddc.varasys.io/releases/. Append ?v=alpha (or ?v=0.0.4, etc.) to any deployment URL to switch versions for one request. See bootstrap/README.md for the install / pin / audit story.
File-naming convention
The full specification — filename format, tracking numbers, revision rules, status codes, folder naming, and the transmittal workflow — lives at https://zddc.varasys.io/reference.html.
Quick example: 123456-EL-SPC-2623_A (IFR) - Specification For Switchgear.pdf
Build & develop
git clone https://codeberg.org/VARASYS/ZDDC.git && cd ZDDC
sh build.sh # build all tools (writes to dist/ only)
sh archive/build.sh # build one tool
sh archive/build.sh --release # cut stable; auto-bumps patch from last tag
sh archive/build.sh --release 0.1.0 # explicit version
sh archive/build.sh --release alpha # cut alpha (mutable channel, no tag)
sh archive/build.sh --release beta # cut beta
npm install && npx playwright install chromium && npm test # tests
./dev-server start # cache-busting HTTP on :8000
Authoritative build/release docs are in AGENTS.md. Architecture notes (single-file rationale, JS module pattern, security model) are in ARCHITECTURE.md. zddc-server (optional Go HTTP server with ACL and a virtual archive index) is in zddc/README.md.
Contributing
ZDDC is an open source project hosted on Codeberg at https://codeberg.org/VARASYS/ZDDC. Bug reports, feature requests, and pull requests welcome.
ZDDC is designed for zero configuration to start and minimal configuration overall — feature proposals are filtered through that lens.
License
GNU Affero General Public License v3.0. Free to use, modify, and distribute, including commercially, under the terms of the license. Provided "as is" without warranty.