fix(cache): restore backend-to-next revalidation and expose revalidation status safely
Deploy Canina / deploy (push) Successful in 1m10s

This commit is contained in:
Canina Automation committed 2026-10-26 15:12:10 +00:00
1 parent 292ed7f920
commit 721118787a
6 files changed
+222 -14

No files matched your search

+7 -3
View File
@@ -105,8 +105,12 @@ if [ ! -s .support-chat.env ]; then
exit 1
fi
# Ensure .revalidation.env exists so compose never fails with missing env file
touch .revalidation.env
# Ensure .revalidation.env exists and is properly provisioned with valid secret
if [ -f "scripts/provision-revalidation-env.py" ]; then
python3 scripts/provision-revalidation-env.py --environment "${BRANCH:-stage}" --source .revalidation.env --output .revalidation.env.tmp 2>/dev/null && mv .revalidation.env.tmp .revalidation.env && chmod 600 .revalidation.env || touch .revalidation.env
else
touch .revalidation.env
fi
# ✅ فایل‌های کانفیگ را از پوشه‌ی scripts مخزن به TARGET_DIR کپی می‌کنیم
echo "Copying configuration files in $TARGET_DIR..."
@@ -134,7 +138,7 @@ BOT_ENV="${TARGET_DIR}/.support-bot.runtime.env"
docker inspect -f '{{range .Config.Env}}{{println .}}{{end}}' canina-bot > "${BOT_ENV}"
chmod 600 "${BOT_ENV}"
echo "Starting containers..."
docker compose up -d --remove-orphans
docker compose up -d --remove-orphans --force-recreate backend_stage frontend_stage
echo "Starting support-chat bot container..."
docker rm -f canina-bot >/dev/null 2>&1 || true
docker run -d --name canina-bot --restart unless-stopped --env-file "${BOT_ENV}" -e HERMES_HOME=/opt/data -e HERMES_RUNTIME_DIR=/opt/hermes/tools -e API_SERVER_HOST=0.0.0.0 -e API_SERVER_PORT=8642 --network traefik_public -v canina_bot_data:/opt/data "${BOT_IMAGE}" gateway run