Use --no-cache in deploy to prevent stale Docker builds
Docker layer caching was serving old site content after git pull because file timestamps didn't change enough to bust the cache. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
a3028a3b51
commit
aa8ad6d106
1 changed files with 1 additions and 1 deletions
|
|
@ -56,7 +56,7 @@ ssh -p "${SSH_PORT}" "${SERVER}" bash <<REMOTE
|
||||||
git pull origin main
|
git pull origin main
|
||||||
|
|
||||||
echo "[remote] Building Docker images..."
|
echo "[remote] Building Docker images..."
|
||||||
docker compose build --parallel --quiet
|
docker compose build --parallel --no-cache
|
||||||
|
|
||||||
echo "[remote] Restarting containers..."
|
echo "[remote] Restarting containers..."
|
||||||
docker compose up -d --remove-orphans
|
docker compose up -d --remove-orphans
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue