OverviewFilesCommitsIssuesDocsReleasesPeers

pear-git commits / 0253dca

Retire pear-git v1 — decommissioned, superseded by pear-git-v3 + pgh
Add a RETIRED marker documenting decommission. Verified 2026-06-20: not running (the live forge process is pear-git-v3 on :5005, not v1), not in tmux/systemd, not a pgh-managed app, nothing in the active stack depends on it. The pear-runtime dep was vestigial (self-update used the in-repo PearGitUpdater), so the #81 OTA migration is moot here — no code change. Nothing deleted: code + ~/.config/pear-git (7M server-data) preserved. Committed locally only — pushing would fire v1's retired CI. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
0253dcaa998d805c63afe4eb6bb28ff3018dd43a
by plankatron <fleeky@gmail.com> · 2026-06-21T00:05:09.000Z

Changed files (1) +38 -0

RETIRED.md +38 -0
……@@ -0,0 +1,38 @@
1# ⛔ RETIRED — pear-git v1 (decommissioned 2026-06-20)
2
3**This repository is the legacy v1 P2P git forge. It is retired and no longer
4deployed, run, or maintained.** It has been fully superseded by:
5
6- **pear-git-v3** (`hyper-fleeky/pear-git-v3`) — the daemon (serves git over
7 `punch://`, hosts issue/org/profile UIs, mirror replication). Runs in
8 production on `:5005` (`server.js serve 5005 --network --prefix=/git`,
9 fronted by `7rnx.net/git`).
10- **pgh** (`hyper-fleeky/pgh`) — the sole CLI surface for the stack.
11
12## Decommission verification (2026-06-20)
13
14Confirmed before retiring — nothing was deleted:
15
16- **Not running.** No `pear-git-server` / v1 `serve` process. The only
17 "pear-git" process on the box is **pear-git-v3** (`pear-git-v3/server.js`),
18 the active forge. v1's port (4040) is not listening; `:5005` is v3.
19- **Not service-managed.** No tmux window, no systemd user unit, not a
20 pgh-managed app (`pgh app list` shows only `pear-git-v3`).
21- **Nothing depends on it.** No package.json in the active stack references
22 `hyper-fleeky/pear-git` v1.
23- **The `pear-runtime` dependency was vestigial** — never instantiated. v1's
24 self-update went through its own `lib/ci/pear-git-updater.js` (`PearGitUpdater`,
25 forge-based), not pear-runtime. So the fleet OTA migration
26 (hyper-fleeky-dev #81) is **moot** for this repo — no code change, no
27 ballooning corestore (`~/.config/pear-git` is 7 MB of forge server-data, not
28 pear-runtime blobs).
29
30## Do NOT
31
32- **Do NOT delete** the code or `~/.config/pear-git` server-data (never-delete
33 rule — preserved for history/forensics).
34- **Do NOT `git push pear|origin`** from here — those remotes' post-receive
35 hooks would fire v1's CI and attempt to build/deploy a retired forge. This
36 marker is committed locally only.
37
38To work on the forge, use **pear-git-v3** + **pgh**.