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:
30
deployment/ansible/playbooks/deploy-complete.yml
Normal file
30
deployment/ansible/playbooks/deploy-complete.yml
Normal file
@@ -0,0 +1,30 @@
|
||||
---
|
||||
# Complete Deployment Playbook
|
||||
# Combines all deployment steps into a single Ansible run:
|
||||
# 1. Deploy Application Code
|
||||
# 2. Deploy Docker Image
|
||||
# 3. Install Composer Dependencies
|
||||
#
|
||||
# This reduces SSH connections and Ansible overhead compared to running
|
||||
# three separate playbook calls.
|
||||
#
|
||||
# Usage:
|
||||
# ansible-playbook -i inventory/production.yml playbooks/deploy-complete.yml \
|
||||
# -e "deployment_environment=staging" \
|
||||
# -e "deployment_hosts=production" \
|
||||
# -e "image_tag=latest" \
|
||||
# -e "docker_registry=registry.michaelschiemer.de" \
|
||||
# -e "docker_registry_username=admin" \
|
||||
# -e "docker_registry_password=password" \
|
||||
# -e "git_branch=staging" \
|
||||
# --vault-password-file /tmp/vault_pass
|
||||
|
||||
# Step 1: Deploy Application Code
|
||||
- import_playbook: deploy-application-code.yml
|
||||
|
||||
# Step 2: Deploy Docker Image
|
||||
- import_playbook: deploy-image.yml
|
||||
|
||||
# Step 3: Install Composer Dependencies
|
||||
- import_playbook: install-composer-dependencies.yml
|
||||
|
||||
Reference in New Issue
Block a user