Date: 2026-02-22 Status: Completed Origin: MDF Webseiten session 0025
/api/backups/offsite was calling run_ops_json() (in-container execution) but ops offsite list requires the host Python venvrun_ops_host_json() helper to ops_runner.py using nsenter-based host executionbackups.py router to use run_ops_host_json() for offsite listingops status CLI output/opt/data/backups/ — changed backup-all.sh to call SL CLI per-env with explicit --backup-dirops commands that require host-side Python venvs — must use nsenter bridge. This is a recurring pattern: in-container vs host execution boundary is an important architectural distinction in the ops-dashboard.run_ops_json() (in-container, fast) and run_ops_host_json() (host via nsenter, required for backup/offsite commands)./opt/data/ops-dashboard/app/ops_runner.py — added run_ops_host_json() helper/opt/data/ops-dashboard/app/routers/backups.py — use host execution for offsite listing/opt/infrastructure/ops — reformatted backup summary with date-grouped Rich tablesTags: #Session #OpsDashboard #BackupSystem #Offsite