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:
@@ -68,6 +68,8 @@ Developer → git push
|
||||
|
||||
## Directory Structure
|
||||
|
||||
### Local Repository Structure
|
||||
|
||||
```
|
||||
deployment/
|
||||
├── ansible/ # Ansible config, playbooks, inventory, templates
|
||||
@@ -90,6 +92,22 @@ deployment/
|
||||
└── README.md (dieses Dokument)
|
||||
```
|
||||
|
||||
### Server Directory Structure
|
||||
|
||||
Auf dem Production-Server existieren zwei Hauptverzeichnisse:
|
||||
|
||||
```
|
||||
/home/deploy/
|
||||
├── deployment/ # Infrastructure-as-Code (24M)
|
||||
│ ├── stacks/ # Docker Compose Stacks
|
||||
│ └── backups/ # Backup-Dateien
|
||||
└── michaelschiemer/ # Application Code (491M)
|
||||
├── current/ # Symlink → Aktuelle deployed Version
|
||||
└── .archive/ # Alte Versionen (Rollback)
|
||||
```
|
||||
|
||||
**📖 Detaillierte Erklärung:** Siehe [docs/server-directory-structure.md](docs/server-directory-structure.md)
|
||||
|
||||
## Getting Started
|
||||
|
||||
### 🧪 Pipeline-Tests vorbereiten
|
||||
|
||||
Reference in New Issue
Block a user