docs: Gitea HTTPS token setup and 2026-10-16 push pointers.
Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
1 parent
2d145c2878
commit
72930e0fd6
1 file changed
+20
-3
@@ -65,9 +65,26 @@ git clone https://a16.ssystems.de/sunfish-admin/sunfish-a16-rom.git
|
||||
cd sunfish-a16-rom && git checkout standby-ksu-split-roadmap
|
||||
```
|
||||
|
||||
Configure `git credential` or a personal access token in Gitea (Settings →
|
||||
Applications) on the new laptop. Without credentials, `git fetch`/`push` fails
|
||||
after nginx Basic.
|
||||
**Git from the laptop** needs Gitea credentials in the HTTPS URL (nginx Basic
|
||||
alone is not enough for `git push`). On first login as `sunfish-admin`, create a
|
||||
**Personal Access Token** (Gitea → Settings → Applications) and either:
|
||||
|
||||
```bash
|
||||
git config --global credential.helper store
|
||||
# first fetch/push: user sunfish-admin, password = token
|
||||
```
|
||||
|
||||
or embed in the remote (keep out of Git):
|
||||
|
||||
`https://sunfish-admin:<TOKEN>@a16.ssystems.de/sunfish-admin/AXP-Resurection.git`
|
||||
|
||||
Host-side pushes can use `/srv/rom/secrets/gitea-admin.txt` (`api_token`) on
|
||||
loopback `127.0.0.1:3000` — laptop does not get that file in Git.
|
||||
|
||||
**Pushed to Gitea (2026-10-16 UTC):** `AXP-Resurection` @ `009-axp-los23-port`
|
||||
→ `2d145c2`; `sunfish-a16-rom` @ `standby-ksu-split-roadmap` → `491fdfb`.
|
||||
Prefer `git clone`/`pull` on the new laptop over the USB tree if the stick
|
||||
predates that push.
|
||||
|
||||
**Branches (2026-10-16):**
|
||||
|
||||
|
||||
Reference in new issue
Block a user