feat(Phase 7): final audit, handoff documentation, project state update
This commit is contained in:
+56
-10
@@ -1,13 +1,59 @@
|
||||
# Next Steps
|
||||
# Next Steps — Production Deployment
|
||||
|
||||
## T07: KI-Copilot — COMPLETED
|
||||
**Datum:** 2026-07-18
|
||||
**Phase:** Post-Phase 7 — Production Deployment
|
||||
|
||||
All acceptance criteria met. No blockers.
|
||||
---
|
||||
|
||||
### Potential Follow-up Tasks
|
||||
- Integration test with real OpenRouter API (requires API key configuration)
|
||||
- Voice transcription with real audio (currently stub when no API key)
|
||||
- Frontend E2E tests with Playwright
|
||||
- Copilot settings panel (model selection, temperature)
|
||||
- Action result rendering in chat (show vehicle/contact search results inline)
|
||||
- Multi-language support for system prompt
|
||||
## 1. Vor Production Deployment (KRITISCH)
|
||||
|
||||
- [ ] **JWT_SECRET generieren**: `openssl rand -hex 32` → in .env / Coolify eintragen
|
||||
- [ ] **POSTGRES_PASSWORD setzen**: Sicheres Passwort wählen
|
||||
- [ ] **CORS_ORIGINS konfigurieren**: Production Frontend-URL eintragen (z.B. `https://erp.ihre-domain.de`)
|
||||
- [ ] **NEXT_PUBLIC_API_URL setzen**: Production Backend-URL (z.B. `https://erp.ihre-domain.de/api/v1`)
|
||||
- [ ] **APP_ENV=production** setzen
|
||||
|
||||
## 2. API-Keys konfigurieren (WICHTIG)
|
||||
|
||||
- [ ] **OPENROUTER_API_KEY** setzen — erforderlich für OCR, Bildretusche, KI-Copilot
|
||||
- [ ] **MOBILE_DE_API_KEY** setzen — erforderlich für mobile.de Push-Sync
|
||||
- [ ] **MOBILE_DE_SELLER_ID** setzen — mobile.de Seller ID
|
||||
|
||||
## 3. Infrastructure (EMPFOHLEN)
|
||||
|
||||
- [ ] **Redis aktivieren** — für async Features (OCR, Retusche, mobile.de Push)
|
||||
- [ ] **Persistent Volume für Uploads** verifizieren (`/data/uploads`)
|
||||
- [ ] **Database Backup-Strategie** definieren (pg_dump cron)
|
||||
- [ ] **SSL/TLS** über Coolify/Traefik verifizieren
|
||||
|
||||
## 4. Deployment ausführen
|
||||
|
||||
- [ ] Coolify Resource erstellen (Docker Compose)
|
||||
- [ ] Environment Variables in Coolify eintragen
|
||||
- [ ] Deploy starten
|
||||
- [ ] Health Check abwarten: `GET /api/v1/health` → 200
|
||||
- [ ] Post-Deploy Verifikation (siehe `docs/handoff.md` Abschnitt 3)
|
||||
|
||||
## 5. Post-Deploy Smoke Test
|
||||
|
||||
- [ ] Login funktioniert
|
||||
- [ ] Fahrzeug anlegen + bearbeiten
|
||||
- [ ] OCR Upload + Ergebnis anwenden
|
||||
- [ ] Kontakt anlegen + USt-IdNr. prüfen
|
||||
- [ ] Datei Upload + Thumbnail
|
||||
- [ ] Verkauf anlegen + Vertrag-PDF
|
||||
- [ ] DATEV-Export herunterladen
|
||||
- [ ] KI-Copilot Chat
|
||||
- [ ] Bildretusche + Preisvergleich
|
||||
- [ ] mobile.de Push (falls API Key gesetzt)
|
||||
|
||||
## 6. Langfristige Aufgaben
|
||||
|
||||
- [ ] E2E-Tests mit Playwright
|
||||
- [ ] Integration-Tests mit echtem OpenRouter API
|
||||
- [ ] BZSt eVatR API-Zugang beantragen
|
||||
- [ ] CI/CD Pipeline (Forgejo Actions)
|
||||
- [ ] Monitoring & Alerting
|
||||
- [ ] Performance-Optimierung
|
||||
- [ ] Task-Graph-Status-Felder korrigieren (Metadata)
|
||||
- [ ] test_report.md für alle Tasks ergänzen
|
||||
Reference in New Issue
Block a user