Dokumentation: Git Push Authentifizierung mit API Token
🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -451,6 +451,28 @@ ports:
|
|||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
### Git Push zu Gitea schlaegt fehl
|
||||||
|
|
||||||
|
**Problem:** `Authentication failed` beim Push zu Gitea
|
||||||
|
|
||||||
|
**Ursache:** Git Credential Manager kann sich nicht authentifizieren
|
||||||
|
|
||||||
|
**Loesung:** API Token verwenden:
|
||||||
|
```bash
|
||||||
|
# Token in Gitea generieren:
|
||||||
|
# Settings -> Applications -> Generate New Token
|
||||||
|
|
||||||
|
# Push mit Token (einmalig)
|
||||||
|
git push https://USERNAME:TOKEN@eckardt-git.duckdns.org/USERNAME/REPO.git master
|
||||||
|
|
||||||
|
# Oder: Remote mit Token setzen (dauerhaft)
|
||||||
|
git remote set-url origin https://USERNAME:TOKEN@eckardt-git.duckdns.org/USERNAME/REPO.git
|
||||||
|
```
|
||||||
|
|
||||||
|
**Hinweis:** Token im Vaultwarden speichern!
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
### Rate Limiting Debugging
|
### Rate Limiting Debugging
|
||||||
|
|
||||||
**Problem:** Unklar ob Rate Limiting greift
|
**Problem:** Unklar ob Rate Limiting greift
|
||||||
|
|||||||
Reference in New Issue
Block a user