ZDDC/.gitignore
ZDDC 76820fa8dd chore: split website out into orphan branch + worktree
Moves website source + release artifacts off `main` and into a new
orphan branch named `website` in this same Codeberg repo. A `git worktree`
of that branch — typically at ~/src/zddc-website/ — is what the system
Caddy now bind-mounts and serves at zddc.varasys.io. Decoupling source
from the live site means editing source can no longer accidentally
affect what's published.

Layout going forward:
- ~/src/zddc/         — main worktree (this branch, source only).
- ~/src/zddc-website/ — git worktree of the `website` branch:
                         hand-edited content + LFS-tracked release
                         artifacts (server binaries) + regular-git
                         HTML tool releases + symlinks.
- Caddy bind-mount swapped: ~/src/zddc/website → ~/src/zddc-website
  (quadlet at /etc/containers/systemd/caddy.container, restarted).

Build pipeline now writes releases to
${ZDDC_DEPLOY_RELEASES_DIR:-$HOME/src/zddc-website/releases}.
- build.sh:                RELEASES_DIR points at the env var
- shared/build-lib.sh:     promote_release honors the env var, falls
                            back to the legacy in-repo path so any
                            standalone single-tool release on a checkout
                            that still has website/ keeps working
- freshen-channel:         passes ZDDC_DEPLOY_RELEASES_DIR through to
                            the worktree-based build

Docs (CLAUDE.md, AGENTS.md, ARCHITECTURE.md, .gitignore) updated for
the new layout. The 51 MB of website/ blobs stays in main's history
(no force-push); over time Codeberg's GC will pack them down.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-02 07:52:20 -05:00

41 lines
1.3 KiB
Text

tossme/
examples/
.env
.vscode
# Per-project Claude Code state (planning files, agent transcripts, etc.)
.claude/
# Session planning (never public)
PLAN.md
# Node dependencies
node_modules/
# Test report and results
playwright-report/
test-results/
# Build artifacts
# NOTE: dist/ is listed here but each tool's dist/*.html is force-tracked in git
# (added with `git add -f tool/dist/tool.html`). This is intentional — built artifacts
# are committed alongside source so users can download them directly from the repo.
# New tool dist files must be force-added: git add -f tool/dist/tool.html
dist/
# The website (hand-edited index.html / reference.html / css/ / js/ / img/
# plus all release artifacts) lives in the orphan `website` branch of this
# same Codeberg repo. A `git worktree` of that branch is typically checked
# out at ~/src/zddc-website/ and is what the system Caddy serves at
# zddc.varasys.io. The lockstep build pipeline writes release artifacts
# directly to ~/src/zddc-website/releases/ (override with
# $ZDDC_DEPLOY_RELEASES_DIR). zddc-server binaries are LFS-tracked on
# the website branch; HTML tools + symlinks stay in regular git.
# IDE and project files
.opencode/
opencode.json
package-lock.json
zddc-knowledge*.json
zddc-knowledge*.md
zddc-knowledge*.html