From eb25d2c34e971394d472c322f52b0b674b64536e Mon Sep 17 00:00:00 2001 From: "ext.jeremy.guillot@maxicoffee.domains" Date: Wed, 11 Mar 2026 21:38:40 +0100 Subject: [PATCH] fix: run cache:clear after docker restart, not before Docker resolves bind mounts at container start time, not dynamically when the Deployer symlink changes. Running cache:clear before restart means docker exec sees the old release code, causing errors on changed config. Co-Authored-By: Claude Sonnet 4.6 --- deploy.php | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/deploy.php b/deploy.php index cec7df2..580f5b0 100644 --- a/deploy.php +++ b/deploy.php @@ -45,13 +45,13 @@ task('webpack_encore:build', function () { }); // Restart Docker containers (entrypoint gère les migrations automatiquement) -// cache:clear avant restart : le nouveau code est déjà visible via bind mount, -// mais var/ est un volume Docker persistant qui garde l'ancien cache Symfony. +// Le cache:clear est fait APRÈS le restart : Docker résout le bind mount au démarrage +// du container, pas dynamiquement. Avant restart, docker exec voit encore l'ancienne release. desc('Restart Docker containers'); task('docker:restart', function () { - run('docker exec mangarr php bin/console cache:clear --env=prod'); run('docker restart mangarr-worker-commands mangarr-worker-events mangarr-worker-scheduler'); run('docker restart mangarr'); + run('docker exec mangarr php bin/console cache:clear --env=prod'); }); // Pas de PHP sur l'hôte : désactiver les tâches Symfony qui en ont besoin