Deploying the Knowledge OS docs site
The HTML docs are generated from this vault's markdown by _meta/scripts/build_html_docs.py and served via nginx (see Dockerfile). Markdown stays the source of truth; HTML is a build artifact.
Hosting options
A. Coolify static app (recommended — gives a real URL with auto-rebuild on push)
The Coolify project "Knowledge OS Docs" already exists. Create the application inside it:
| Field | Value |
|---|---|
| Project | Knowledge OS Docs |
| Server | runner-103.243.116.249 (uuid x9dcph0q2mtwql9illb6umkp) |
| Source | Private GitLab → aspire/knowledge-os-vault |
| Branch | main |
| Build pack | Dockerfile |
| Port exposed | 80 |
| Domain | ko-docs.aspiredigital.group (or your preference) |
Then add a Cloudflare A record: ko-docs.aspiredigital.group → 103.243.116.249 (DNS-only/grey-cloud or proxied as you prefer).
Why this needs a human (or explicit auth): the vault is a private GitLab repo, so Coolify must clone it with a credential (the Aspire pattern embeds a glpat- PAT in the clone URL). Agents are blocked from materializing that PAT automatically — paste it in the Coolify UI, or tell the agent "use the GitLab PAT for the Coolify URL" to authorize it for this one call.
B. GitLab Pages (already wired, just not served)
.gitlab-ci.yml has a pages job that builds the same site (verified green, 56 pages). It only needs GitLab Pages enabled instance-wide (pages_external_url + wildcard DNS + cert in the GitLab Omnibus config). Once enabled, every push to main publishes automatically — no Coolify needed.
C. Local / build-only
KO_VAULT=$PWD KO_OUT=public python3 _meta/scripts/build_html_docs.py && open public/index.html or download artifacts.zip from the latest pages pipeline.