chore: remove all gitea remote references; single origin push only
Some checks failed
Build + Deploy / build-admin-compliance (push) Failing after 45s
Build + Deploy / build-backend-compliance (push) Successful in 13s
Build + Deploy / build-ai-sdk (push) Successful in 40s
Build + Deploy / build-developer-portal (push) Successful in 12s
Build + Deploy / build-tts (push) Successful in 11s
Build + Deploy / build-document-crawler (push) Successful in 14s
Build + Deploy / build-dsms-gateway (push) Successful in 12s
Build + Deploy / trigger-orca (push) Has been skipped
CI/CD / loc-budget (push) Successful in 21s
CI/CD / guardrail-integrity (push) Has been skipped
CI/CD / go-lint (push) Has been skipped
CI/CD / python-lint (push) Has been skipped
CI/CD / nodejs-lint (push) Has been skipped
CI/CD / test-go-ai-compliance (push) Successful in 48s
CI/CD / test-python-backend-compliance (push) Failing after 38s
CI/CD / test-python-document-crawler (push) Successful in 31s
CI/CD / test-python-dsms-gateway (push) Successful in 27s
CI/CD / sbom-scan (push) Has been skipped
CI/CD / validate-canonical-controls (push) Successful in 19s

There is only one remote (origin). Removed all occurrences of:
  - git push gitea / git push origin main && git push gitea main
  - "Pushing to gitea (external)" in deploy.sh
  - # gitea: git@gitea.meghsakha.com:... remote comment in docs-src/index.md
  - "Push auf gitea triggert" → "Push auf origin triggert" in docs
  - Clone URL updated to ssh://git@coolify.meghsakha.com:22222/... in
    README.md and CONTRIBUTING.md

Web UI URLs (gitea.meghsakha.com/...) are unchanged — those are still valid.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Sharang Parnerkar
2026-04-19 16:16:12 +02:00
parent 8266c37911
commit 8ec8af4c2d
12 changed files with 27 additions and 33 deletions

View File

@@ -24,7 +24,7 @@ Uebersicht ueber den Deployment-Prozess fuer BreakPilot Compliance.
│ ├── developer-portal/ (Next.js) │
│ └── docs-src/ (MkDocs) │
│ │
│ git push origin main && git push gitea main
│ git push origin main │
└───────────────────────────────┬─────────────────────────────────┘
│ git push
@@ -63,12 +63,12 @@ Uebersicht ueber den Deployment-Prozess fuer BreakPilot Compliance.
```bash
# Code auf MacBook bearbeiten
# Committen und zu beiden Remotes pushen:
git push origin main && git push gitea main
git push origin main
```
### 2. Automatische Tests (Gitea Actions)
Push auf gitea triggert automatisch die CI-Pipeline:
Push auf origin triggert automatisch die CI-Pipeline:
- **Go Tests:** `ai-compliance-sdk` Unit Tests
- **Python Tests:** `backend-compliance`, `document-crawler`, `dsms-gateway`

View File

@@ -207,7 +207,7 @@ Runtime-Betrieb: Qdrant-RAG für semantische Suche, Chat, Scope-Analyse
2. Mac Mini: Control-Generierung → PostgreSQL (shared, 46.225.100.82:54321)
3. QA: PDF-Match, Dedup, Source-Normalisierung
4. Qdrant Migration: macmini:6333 → qdrant-dev.breakpilot.ai (scripts/migrate-qdrant.py)
5. Deploy: git push gitea → Orca Build + Deploy
5. Deploy: → Orca Build + Deploy
```
**WICHTIG:** PostgreSQL ist SHARED — Änderungen auf Mac Mini sind sofort in Production sichtbar. Qdrant hat getrennte Instanzen (lokal + production) und muss manuell synchronisiert werden.

View File

@@ -92,7 +92,7 @@ Module die Compliance-Kunden im SDK sehen und nutzen:
```bash
# Production (Orca — Standardweg):
git push origin main && git push gitea main
git push origin main
# Orca baut und deployt automatisch.
# Lokal (Mac Mini — nur Dev/Tests):
@@ -105,11 +105,11 @@ docker compose -f breakpilot-compliance/docker-compose.yml up -d
```bash
# Zwei Remotes - IMMER zu beiden pushen:
git push origin main && git push gitea main
git push origin main
# Remotes:
# origin: http://macmini:3003/pilotadmin/breakpilot-compliance.git
# gitea: git@gitea.meghsakha.com:Benjamin_Boenisch/breakpilot-compliance.git
```
---