Phase 1a infrastructure for building and hosting BlumeOps docs: - Add quartz.config.ts and quartz.layout.ts for Quartz configuration - Add containers/quartz/ with nginx-based static site server that downloads release bundles on startup via DOCS_RELEASE_URL env var - Add .forgejo/workflows/build-blumeops.yaml workflow (manual trigger) that builds Quartz site and creates Forgejo release with tarball - Update docs/README.md with finalized tooling choice and split Phase 1 into 1a (CI) and 1b (CD/hosting) The architecture separates content versioning from infrastructure: - Releases are versioned BlumeOps releases (v1.0.0, etc.) - Doc tarballs are attached as release assets - The quartz container is a generic static site server Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| devpi | ||
| forgejo-runner | ||
| kiwix-serve | ||
| kubectl | ||
| miniflux | ||
| nettest | ||
| quartz | ||
| teslamate | ||
| transmission | ||