fix: Gitea Traefik routing and connection pool optimization
Some checks failed
🚀 Build & Deploy Image / Determine Build Necessity (push) Failing after 10m14s
🚀 Build & Deploy Image / Build Runtime Base Image (push) Has been skipped
🚀 Build & Deploy Image / Build Docker Image (push) Has been skipped
🚀 Build & Deploy Image / Run Tests & Quality Checks (push) Has been skipped
🚀 Build & Deploy Image / Auto-deploy to Staging (push) Has been skipped
🚀 Build & Deploy Image / Auto-deploy to Production (push) Has been skipped
Security Vulnerability Scan / Check for Dependency Changes (push) Failing after 11m25s
Security Vulnerability Scan / Composer Security Audit (push) Has been cancelled
Some checks failed
🚀 Build & Deploy Image / Determine Build Necessity (push) Failing after 10m14s
🚀 Build & Deploy Image / Build Runtime Base Image (push) Has been skipped
🚀 Build & Deploy Image / Build Docker Image (push) Has been skipped
🚀 Build & Deploy Image / Run Tests & Quality Checks (push) Has been skipped
🚀 Build & Deploy Image / Auto-deploy to Staging (push) Has been skipped
🚀 Build & Deploy Image / Auto-deploy to Production (push) Has been skipped
Security Vulnerability Scan / Check for Dependency Changes (push) Failing after 11m25s
Security Vulnerability Scan / Composer Security Audit (push) Has been cancelled
- Remove middleware reference from Gitea Traefik labels (caused routing issues) - Optimize Gitea connection pool settings (MAX_IDLE_CONNS=30, authentication_timeout=180s) - Add explicit service reference in Traefik labels - Fix intermittent 504 timeouts by improving PostgreSQL connection handling Fixes Gitea unreachability via git.michaelschiemer.de
This commit is contained in:
26
deployment/docs/tests/README.md
Normal file
26
deployment/docs/tests/README.md
Normal file
@@ -0,0 +1,26 @@
|
||||
# Test-Dokumentation
|
||||
|
||||
Dieses Verzeichnis enthält historische Test-Dokumentationen für verschiedene Deployment-Szenarien.
|
||||
|
||||
## Status
|
||||
|
||||
Die meisten Dokumentationen in diesem Verzeichnis sind **veraltet** und beziehen sich auf alte Deployment-Pfade (`stacks/application` statt `stacks/production`).
|
||||
|
||||
## Aktuelle Test-Prozesse
|
||||
|
||||
Für aktuelle Test-Prozesse siehe:
|
||||
- **[deployment/docs/guides/deployment-commands.md](../guides/deployment-commands.md)** - Aktuelle Deployment-Befehle
|
||||
- **[deployment/README.md](../../README.md)** - Haupt-Dokumentation mit Quick Start
|
||||
|
||||
## Historische Dokumentationen
|
||||
|
||||
Die folgenden Dateien sind historisch und können als Referenz dienen:
|
||||
- `quick-test.md` - Schnelle Test-Anleitung (veraltet)
|
||||
- `git-deployment-test.md` - Git-Deployment Tests (veraltet)
|
||||
- `test-git-deployment.md` - Weitere Git-Deployment Tests (veraltet)
|
||||
- `git-deployment-issue.md` - Problem-Dokumentation (veraltet)
|
||||
- `recommended-test-flow.md` - Empfohlener Test-Workflow (veraltet)
|
||||
- `test-results.md` - Test-Ergebnisse (veraltet)
|
||||
|
||||
**Hinweis:** Diese Dokumentationen verweisen auf alte Pfade und sollten nicht mehr direkt verwendet werden.
|
||||
|
||||
Reference in New Issue
Block a user