| 2026-09-10 |
Document /backup and ZIP-update in mardisbot remote ops
...
mardisbot.md remote ops section extended: /backup (download code as ZIP) and ZIP-upload update (auto-backup, auto-rollback, .env/venv untouched) now available via MardisOpsBot v2.
|
MardisOpsBot v2 deployed: /backup + ZIP-update, sudoers stop/start, unit ReadWritePaths; tests 18/18
...
v2 deployed to VM tg_bots: /backup + ZIP-update added, sudoers gained stop/start, unit gained ReadWritePaths for MardisBot dir; sandbox tests 18/18 passed. Verified live via SSH.
|
Document NoNewPrivileges fix in mardisops unit
...
mardisopsbot.md: documented removal of NoNewPrivileges=true (it blocked sudo inside the service, broke /status) and the enrolled admin user_id 78389352.
|
Cross-link MardisOpsBot from mardisbot doc
...
Cross-link in mardisbot.md to the new MardisOpsBot remote ops channel (doc 10-systems/bots/mardisopsbot.md).
|
Add MardisOpsBot (mardisops.service) on VM tg_bots
...
Deployed MardisOpsBot on VM tg_bots (192.168.1.254): mardisops.service active (running), enabled; files in /home/ubuntu/bots/MardisOpsBot; sudoers grant /etc/sudoers.d/99-mardisops-sudoers installed and validated. Documented in 10-systems/bots/mardisopsbot.md and services inventory.
|
MardisBot is ACTIVE on VM tg_bots (192.168.1.254); correct host and status
...
Live verification 2026-09-10: MardisBot is running on VM tg_bots (192.168.1.254), not on the tgbots VPS (192.168.1.178). Previous 'missing' status was wrong — the bot was redeployed to the VM after the VPS rebuild.
|
Mark MardisBot as not deployed after 2026-09-10 tgbots audit
...
Exhaustive read-only audit of tgbots (192.168.1.178) on 2026-09-10: no bot processes, no bot systemd units (mardisbot.service absent, no journal history), only marginator docker stack, no cron/tmux/screen, no bot project dirs, zero bot-token matches across /home /opt /srv /etc /usr/local /var, no Telegram API outbound connections, no telegram libraries installed. Host rebuilt ~2026-08-27 and MardisBot was never redeployed.
|