fix: COMPOSE_DIR corrigé dans gitea-auto-update.sh + credentials paramétrés

- COMPOSE_DIR aligné sur le vrai chemin (~/dev/git/outils/docker/gitea)
- Backup pré-update utilise DB_CONTAINER/DB_ROOT_PASSWORD/DB_NAME
- Ajout set -euo pipefail dans backup-docker.sh
This commit is contained in:
2026-06-26 12:52:06 -04:00
parent 33d6c5d266
commit 63e7debb52
2 changed files with 19 additions and 2 deletions
+14
View File
@@ -0,0 +1,14 @@
#!/bin/bash
set -euo pipefail
BACKUP_DIR="/NFS/BACKUPS"
DATE=$(date +%Y%m%d)
mkdir -p $BACKUP_DIR
docker run --rm -v jellyfin_data:/source -v $BACKUP_DIR:/backup alpine \
tar czf /backup/jellyfin-$DATE.tar.gz /source
docker run --rm -v shaarli_data:/source -v $BACKUP_DIR:/backup alpine \
tar czf /backup/shaarli-$DATE.tar.gz /source
# Vérification
ls -lh $BACKUP_DIR | grep -E "jellyfin|shaarli"
+5 -2
View File
@@ -11,7 +11,7 @@
set -euo pipefail
# ─── Configuration (modifiable) ─────────────────────────────────────────────
COMPOSE_DIR="${COMPOSE_DIR:-$HOME/dev/git/outils/gitea}"
COMPOSE_DIR="${COMPOSE_DIR:-$HOME/dev/git/outils/docker/gitea}"
COMPOSE_FILE="${COMPOSE_FILE:-docker-compose.yml}"
CONTAINER_NAME="${CONTAINER_NAME:-gitea_server}"
IMAGE_NAME="${IMAGE_NAME:-gitea/gitea}"
@@ -23,6 +23,9 @@ TELEGRAM_CHAT_ID="${TELEGRAM_CHAT_ID:-}"
NTPY_TOPIC="${NTPY_TOPIC:-}"
HEALTH_CHECK_URL="${HEALTH_CHECK_URL:-http://localhost:3000}"
HEALTH_CHECK_TIMEOUT="${HEALTH_CHECK_TIMEOUT:-30}"
DB_CONTAINER="${DB_CONTAINER:-gitea_db}"
DB_NAME="${DB_NAME:-gitea}"
DB_ROOT_PASSWORD="${DB_ROOT_PASSWORD:-gitea}"
# ─── Logging ─────────────────────────────────────────────────────────────────
log() {
@@ -88,7 +91,7 @@ BACKUP_PRE_DIR="${BACKUP_PRE_DIR:-/tmp/gitea-pre-update-$(date +%Y%m%d-%H%M%S)}"
mkdir -p "$BACKUP_PRE_DIR"
log "💾 Backup pré-update vers $BACKUP_PRE_DIR"
docker exec gitea_db mysqldump -u root -pgitea gitea > "$BACKUP_PRE_DIR/gitea_db.sql" 2>/dev/null || {
docker exec "$DB_CONTAINER" mysqldump -u root -p"$DB_ROOT_PASSWORD" "$DB_NAME" > "$BACKUP_PRE_DIR/gitea_db.sql" 2>/dev/null || {
log "⚠️ Backup pré-update DB échoué, on continue quand même"
}