coulomb/ops-warden
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Document Forgejo clone, install, and upgrade steps in README.

Browse Source 
Canonical source is forgejo.coulomb.social; includes SSH remote config,
make install-all, release upgrade path, and stale-wheel recovery.
This commit is contained in:
Bernd Worsch
2026-07-07 16:57:39 +02:00
parent 885385adf3
commit 4976002f9c
1 changed files with 61 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

61
README.md
View File

@@ -9,8 +9,41 @@ See `INTENT.md` for direction, `SCOPE.md` for current implementation, and
and routes every other credential need to its owner — see `wiki/AccessRouting.md`.
Latest gap analysis: `history/2026-06-17-post-wp0007-reassessment.md`.
## Get the source (Forgejo)
Canonical repo: `https://forgejo.coulomb.social/coulomb/ops-warden`
Releases: `https://forgejo.coulomb.social/coulomb/ops-warden/releases`
**HTTPS clone:**
```bash
git clone https://forgejo.coulomb.social/coulomb/ops-warden.git ~/ops-warden
cd ~/ops-warden
```
**SSH clone** (recommended for push/pull; add to `~/.ssh/config` if missing):
```sshconfig
Host forgejo-remote
HostName 92.205.62.239
Port 30022
User git
IdentityFile ~/.ssh/id_gitea
StrictHostKeyChecking accept-new
```
```bash
git clone forgejo-remote:coulomb/ops-warden.git ~/ops-warden
cd ~/ops-warden
```
Legacy Gitea remotes (`gitea-remote`, `gitea.coulomb.social`) still work during
migration; new checkouts should use Forgejo.
## Install
From a Forgejo checkout:
**Recommended** (warden + experiential memory for route/worker/agent sessions):
```bash
@@ -41,6 +74,34 @@ phase-memory must be a sibling checkout at `../phase-memory` by default, or set
`PHASE_MEMORY_REPO` when running make. Opt out of memory at runtime with
`WARDEN_MEMORY=0`.
### Upgrade after a release
When a new tag is published on Forgejo (e.g. `v0.1.1`):
```bash
cd ~/ops-warden
git fetch --tags origin
git pull --ff-only
make install-all
warden route list # sanity check the installed CLI
```
If `warden` still behaves like an older build (same version string but missing
recent subcommands or fixes), clear the cached wheel and reinstall:
```bash
uv cache clean ops-warden
uv tool install . --with-editable ../phase-memory --reinstall --force
```
Check out a specific release:
```bash
git fetch --tags origin
git checkout v0.1.1
make install-all
```
## Quick start (local backend)
```bash