Anya Tokugawa d5d21b7841
Build and publish container images / images (push) Successful in 9m34s
Release container images / release (push) Successful in 36s
Refactor architecture into eight components and consolidate reliability work
Extract Grammaratur, Dregarnuhr, Geduldh, Mestionora, Ordoschnellic, Schutzaria, Kunstzeal and Seheweit behind compatible application contracts.

Include accumulated editor resilience, navigation and theme UX, remote CLI, storage/schema and DR groundwork, tests and design/operations documentation.

Verified: uncached full Go suite; go vet ./...; race tests for all eight components; 11 targeted Chromium tests; Node suites; 19 Python CLI tests; reproducible editor build. No push, release tag or deployment in this checkpoint.
2026-11-01 15:23:31 +09:00

pageswiki

Simplest and powerful wiki architecture for personal

Container CI

Gitea Actions tests and builds the application, adaptor gateway, and Excalidraw viewer, then publishes them to the Gitea container registry with commit-SHA tags. See Gitea image builds and registry setup for runner requirements, registry secrets, and the optional registry Compose overlay. The workflow does not deploy to production.

PagesWiki follows Semantic Versioning 2.0.0. Release tags (starting with v0.1.0) promote existing tested images without rebuilding. See the versioning and release policy.

Knowledge City Model

Pages Wiki uses urban language for its content hierarchy:

Campus → Domain → Zone (Quartier / Street) → Spot → Page
  • Campus manages a group of Domains.
  • Domain is a site space selected by a host or subdomain.
  • Zone is the managed tree containing Quartiers and Streets.
  • Quartier is a planned aggregation of Streets.
  • Street groups Spots as the smallest city block.
  • Spot is the smallest knowledge group.
  • Page is the smallest knowledge unit and is identified by UUID, not path.

A Page may be linked from multiple Spots. Semantic paths are projections and must not be treated as Page identity.

Data CLI

The CLI in data/pageswiki-cli provides rsync-like transfers and an interactive Semantic Path shell over SQLite and data/documents/:

data/pageswiki-cli put article.html path:/quartier/street/spot/page
data/pageswiki-cli get path:/quartier/street/spot/page article.html
data/pageswiki-cli shell
PAGESWIKI_DOMAIN=engineering data/pageswiki-cli ls /

The shell supports ls, cd, cat, view, edit, transfer, Revision, diff/restore, and link commands, with tab completion and persistent history. view uses PAGER; edit uses EDITOR.

Set PAGESWIKI_DATA_DIR when inspecting a different data directory. PAGESWIKI_DOMAIN selects the active Domain by name, UUID, or host. In the interactive shell, domain [NAME|UUID|HOST] displays or changes it.

An instance can enroll into a Controller Campus during container startup:

The included Docker Compose configuration enrolls app2 into a Controller Campus. Copy .env.example to .env and set PAGESWIKI_EXTERNAL_CAMPUS_TOKEN to the controller-issued enrollment token before running Compose. The token is intentionally not committed; .env is excluded from Git and Docker build contexts. Keep it private (for example, chmod 600 .env).

PAGESWIKI_INSTANCE_FQDN=node.example.test \
  pageswiki --add-external-campus campus.example.test "$CAMPUS_TOKEN"

For an explicitly trusted development network without TLS:

PAGESWIKI_INSTANCE_FQDN=node.internal.test \
  pageswiki --add-external-campus-http campus.internal.test "$CAMPUS_TOKEN"

For a node dedicated to externally managed Domains, add --no-default-campus. Its bootstrap Campus and Domain remain while approval is pending, then are removed after the first assigned Domain is pulled:

PAGESWIKI_INSTANCE_FQDN=node.internal.test \
  pageswiki --no-default-campus \
  --add-external-campus-http campus.internal.test "$CAMPUS_TOKEN"

The controller records the instance public-key fingerprint. Domain placement only offers instances whose fingerprint has been approved.

2026-11-09 05:49:44 +09:00
Languages
Go 79.9%
JavaScript 8.3%
Go Template 6.2%
Python 3.6%
CSS 1.9%