Fix: Wartungsmodus immer aktiv während Cache-Rebuild – kein 404 mehr
artisan down/up umschließt jetzt immer fix_permissions, nicht nur bei Migrations/Composer/PHP-Restart. Requests während optimize:clear+optimize bekommen 503 statt 404 durch fehlenden Bootstrap-Cache. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>main v1.1.342
parent
b0daf839d9
commit
a96d8f690a
|
|
@ -426,11 +426,9 @@ if [[ $NEED_FRONTEND -eq 1 ]]; then
|
|||
fi
|
||||
fi
|
||||
|
||||
# -------- Wartungsmodus: Migrations + Cache + PHP-FPM reload -----------------
|
||||
if [[ $NEED_MIGRATIONS -eq 1 || $NEED_PHP_RESTART -eq 1 || $NEED_COMPOSER -eq 1 ]]; then
|
||||
artisan_down
|
||||
MAINTENANCE_ACTIVE=1
|
||||
fi
|
||||
# -------- Wartungsmodus immer aktivieren (Cache-Rebuild darf keine Requests sehen) ---
|
||||
artisan_down
|
||||
MAINTENANCE_ACTIVE=1
|
||||
|
||||
if [[ $NEED_MIGRATIONS -eq 1 ]]; then
|
||||
echo "[i] DB-Migrationen …"
|
||||
|
|
@ -446,8 +444,6 @@ NEW_VER="$(get_version)"
|
|||
write_version_files "$NEW_VER" "$NEW_REV"
|
||||
|
||||
# -------- Rechte + Cache aufbauen (VOR PHP-FPM Restart) ----------------------
|
||||
# fix_permissions: chown aller App-Dirs + optimize:clear + optimize
|
||||
# PHP-FPM startet erst danach → kein Request trifft kaputte/leere Caches
|
||||
fix_permissions
|
||||
|
||||
# -------- Dienste neu laden (gezielt) ----------------------------------------
|
||||
|
|
@ -463,10 +459,8 @@ if [[ $NEED_FRONTEND -eq 1 || $NEED_PHP_RESTART -eq 1 ]]; then
|
|||
fi
|
||||
|
||||
# -------- Wartungsmodus beenden ----------------------------------------------
|
||||
if [[ "$MAINTENANCE_ACTIVE" -eq 1 ]]; then
|
||||
artisan_up
|
||||
MAINTENANCE_ACTIVE=0
|
||||
fi
|
||||
artisan_up
|
||||
MAINTENANCE_ACTIVE=0
|
||||
echo "[✓] Update abgeschlossen: ${OLD_VER} → ${NEW_VER} (${OLD_REV:0:7} → ${NEW_REV:0:7})"
|
||||
|
||||
# -------- .env: REVERB-Werte auf Domain-Basis normalisieren -------------------
|
||||
|
|
|
|||
Loading…
Reference in New Issue