Mike Swanson
0c000109dc
Compressed memory store 104 -> 71 files via four passes: - Syncro: 19 scattered feedback_syncro_* files merged into 3 rule files (api/billing/workflow) + an on-demand feedback_syncro_history.md for incident detail, quotes, and tech/product ID tables. - Four near-duplicate merges: Howard paste-safety, Pluto build server, Howard backend deferral, IX server access (ssh+tailscale). - Per-cluster rule/state/history split applied to GuruConnect (2->1), Dataforth (3->2), Cascades (7->3), GuruRMM (13->3). - New reference_resource_map.md: single auto-loaded cheatsheet for "do I have access to X and how do I connect from this machine?" - MEMORY.md rewritten to match the new layout. Health: broken backlinks 8->7, overlap clusters 12->5, orphans 17->0.
13 lines
1.0 KiB
Markdown
13 lines
1.0 KiB
Markdown
---
|
|
name: reference_gitea_api_credential
|
|
description: Gitea API auth (PRs, merges) uses services/gitea-howard.sops.yaml, NOT the gururmm server SSH password
|
|
metadata:
|
|
type: reference
|
|
---
|
|
|
|
For Gitea API operations as Howard (create/merge PRs, delete branches, etc.), authenticate against the **internal** endpoint `http://172.16.3.20:3000/api/v1` (the public `git.azcomputerguru.com` is Cloudflare-fronted and blocks non-browser API calls) with basic auth `howard:<pw>` where the password comes from **`services/gitea-howard.sops.yaml` field `credentials.password`** (Howard's site-admin Gitea account).
|
|
|
|
Do NOT use `infrastructure/gururmm-server.sops.yaml credentials.password` for Gitea — that is the `guru` server SSH/sudo password for 172.16.3.30. It was rejected by the Gitea API for a write (PR merge) on 2026-05-31; the gitea-howard credential is the correct one. The two are separate accounts; don't assume they're interchangeable.
|
|
|
|
Related: [[reference_gururmm]] (the guru SSH/server password), [[reference_coord_messages_api_shape]].
|