From 4f66508d8656d1c42112b941b1f196157a68541a Mon Sep 17 00:00:00 2001 From: rob thijssen Date: Wed, 22 Apr 2026 12:32:10 +0300 Subject: [PATCH] docs(generic): document Gitea (git.lair.cafe) as default source host Note that new projects default to the self-hosted Gitea instance at git.lair.cafe (git.internal on the WireGuard mesh), that legacy projects on GitHub/GitLab are being migrated as they come up for refactor, and that relocated repos should carry a prominent pointer to the new URL. Co-Authored-By: Claude Opus 4.7 (1M context) --- generic.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/generic.md b/generic.md index 0137412..f9a65ff 100644 --- a/generic.md +++ b/generic.md @@ -476,6 +476,12 @@ This is the environment these apps deploy into. Claude Code should assume it. - SELinux enforcing per §10. - Podman quadlets for containerised workloads; bare-metal systemd units for native Rust binaries (preferred where feasible). +### Source hosting +- **New projects are hosted on the self-hosted Gitea instance** at `git.lair.cafe` (or `git.internal` on the WireGuard mesh — both resolve to the same instance). Agentic contributors will usually have MCP access to this Gitea and should prefer it over any public forge when creating repos, issues, or PRs. +- **Legacy projects** live under various GitHub / GitLab orgs tied to my public username (`grenade`). These will continue to exist but are being migrated to Gitea over time, especially when they come up for a refactor. +- **When a project has been relocated**, the original public repo should carry a prominent notice at the top of its `README.md` (or a GitHub archival notice) pointing to the new Gitea URL. If you're working in a repo that looks stale or superseded, check for such a notice before assuming it's still the canonical location. +- Default to `git.lair.cafe` / `git.internal` for new scaffolds. Only push a new project to GitHub/GitLab if there's a specific reason (OSS visibility, CI integration that only the public forge offers, etc.) — and note the reason in the project README. + --- ## 12. Code Quality and Tooling @@ -532,4 +538,5 @@ When scaffolding or extending a project: 11. SELinux stays enforcing. Work with the default policy first; ship a custom module only when necessary (§10). Never suggest `setenforce 0`. 12. Prefer fewer dependencies. Prefer bare-metal systemd over containers unless there's a reason. 13. Commit in Conventional Commits syntax. Commit autonomously when the work is done; hold off when follow-ups on the same topic are likely (§12 Commits). -14. When unsure, ask — these preferences are defaults, not mandates, but deviations should be deliberate. +14. Default new repos to `git.lair.cafe` / `git.internal` (self-hosted Gitea). Public forges only with a stated reason (§11 Source hosting). +15. When unsure, ask — these preferences are defaults, not mandates, but deviations should be deliberate.