Michael Schiemer
76ec4cf28d
Some checks failed
🚀 Build & Deploy Image / Determine Build Necessity (push) Successful in 52s
Security Vulnerability Scan / Check for Dependency Changes (push) Successful in 51s
🚀 Build & Deploy Image / Build Runtime Base Image (push) Successful in 10s
🚀 Build & Deploy Image / Run Tests & Quality Checks (push) Has been skipped
Security Vulnerability Scan / Composer Security Audit (push) Has been skipped
🚀 Build & Deploy Image / Build Docker Image (push) Successful in 12s
🚀 Build & Deploy Image / Auto-deploy to Staging (push) Failing after 52s
🚀 Build & Deploy Image / Auto-deploy to Production (push) Has been skipped
- Add Docker daemon configuration to use HTTP for git.michaelschiemer.de:5000 registry - Configure insecure-registries in /etc/docker/daemon.json - Add GIT_BRANCH environment variable (staging for staging, main for production) - Set default GIT_REPOSITORY_URL if not provided - Fixes 'http: server gave HTTP response to HTTPS client' error - Fixes missing GIT_BRANCH variable warnings
Ansible Playbooks - Übersicht
Verfügbare Playbooks
Infrastructure Setup
setup-infrastructure.yml- Deployed alle Stacks (Traefik, PostgreSQL, Redis, Registry, Gitea, Monitoring, Production)setup-production-secrets.yml- Deployed Secrets zu Productionsetup-ssl-certificates.yml- SSL Certificate Setupsetup-wireguard-host.yml- WireGuard VPN Setupsync-stacks.yml- Synchronisiert Stack-Konfigurationen zum Server
Deployment & Updates
rollback.yml- Rollback zu vorheriger Versionbackup.yml- Erstellt Backups von PostgreSQL, Application Data, Gitea, Registrydeploy-image.yml- Docker Image Deployment (wird von CI/CD Workflows verwendet)
Maintenance
system-maintenance.yml- System-Updates, Unattended-Upgrades, Docker-Pruningtroubleshoot.yml- Unified Troubleshooting mit Tagsupdate-gitea-config.yml- Aktualisiert Gitea-Konfiguration und startet neu
WireGuard
generate-wireguard-client.yml- Generiert WireGuard Client-Configwireguard-routing.yml- Konfiguriert WireGuard Routing
Initial Deployment
sync-application-code.yml- Rsync-basiertes Code-Sync für Initial Deployment (synchronisiert Code vom lokalen Repository zum Server)deploy-application-code.yml- Git-basiertes Code-Deployment (für CI/CD und zukünftige Deployments)install-composer-dependencies.yml- Installiert Composer Dependencies im PHP Containerbuild-initial-image.yml- Build und Push des initialen Docker Images (für erstes Deployment)
Code Deployment
sync-application-code.yml- Rsync-basiertes Code-Sync (Initial Deployment)deploy-application-code.yml- Git-basiertes Code-Deployment (CI/CD)deploy-image.yml- Docker Image Deployment zu Application Stack
Troubleshooting & Diagnostics
check-container-logs.yml- Container Logs prüfen (queue-worker, web, scheduler)check-container-status.yml- Container Status prüfencheck-final-status.yml- Finale Status-Prüfung aller Containerfix-container-issues.yml- Container-Probleme beheben (Composer Dependencies, Permissions)fix-web-container.yml- Web Container Permissions behebenrecreate-containers-with-env.yml- Container mit env_file neu erstellensync-and-recreate-containers.yml- Docker Compose sync und Container recreate
CI/CD & Development
setup-gitea-runner-ci.yml- Gitea Runner CI Setupsetup-gitea-initial-config.yml- Gitea Initial Setup (automatisiert via app.ini + CLI)setup-gitea-repository.yml- Erstellt Repository in Gitea und konfiguriert Git-Remote (automatisiert via API)update-gitea-config.yml- Aktualisiert Gitea-Konfiguration (Cache, Connection Pooling) zur Behebung von Performance-Problemeninstall-docker.yml- Docker Installation auf Server
Entfernte/Legacy Playbooks
Die folgenden Playbooks wurden entfernt, da sie nicht mehr benötigt werden:
build-and-push.ymlremove-framework-production-stack.ymlremove-temporary-grafana-ip.yml
Verwendung
cd deployment/ansible
ansible-playbook -i inventory/production.yml playbooks/<playbook>.yml