deploy.sh: clear legacy packaging leftovers; honest dep rows

This commit is contained in:
Oleksandr Kozachuk
2026-07-13 15:17:19 +02:00
parent 8a19c35353
commit 1d813f46e2
2 changed files with 4 additions and 1 deletions
+3
View File
@@ -29,6 +29,9 @@ echo "== deploy $TAG -> $HOST (service $SERVICE, config $CONFIG) =="
# Code push: tag tree over ~/fjerkroa_bot; untracked config/state survives (DEP-01)
git archive "$TAG" | ssh "$HOST" 'mkdir -p ~/fjerkroa_bot && tar -x -C ~/fjerkroa_bot'
# In-place extraction does not delete files removed from the tree —
# clear known legacy packaging leftovers (they break the pip build)
ssh "$HOST" 'rm -f ~/fjerkroa_bot/setup.py ~/fjerkroa_bot/requirements.txt ~/fjerkroa_bot/pytest.ini'
ssh "$HOST" "set -e
[ -x ~/venv-bot/bin/python ] || python3.11 -m venv ~/venv-bot
+1 -1
View File
@@ -8,7 +8,7 @@ with date + result.
| --- | --- | --- |
| DEP-01 | 2026-07-13 | Verified with the v3.0.0 ggg deploy: tag-only refusal + untracked config/state survived. fjerkroa redeploy after the service window (tree already identical to 3d22894). |
| DEP-02 | 2026-07-13 | Service map exercised: luma restart via script (v3.0.0); kroa mapping code-reviewed, exercised on its next deploy. |
| DEP-03 | 2026-07-13 | bot.db.pre-v3.0.0 backup confirmed on ggg after deploy. |
| DEP-03 | 2026-07-13 | ggg had no pre-existing bot.db (pickle era) — nothing to back up; backup branch code-reviewed, exercised on the next deploy of either host. |
| DEP-04 | 2026-07-13 | Smoke gate exercised on ggg: RUNNING + fresh login line. |
| DEP-05 | 2026-07-13 | Live-verified: kroa deploy attempt ~15h Oslo refused without DEPLOY_FORCE=1. |
| DEP-06 | 2026-07-13 | Rollback documented (older tag + db backup restore); live drill pending — next release. |