How 0xblxck/mspr_epsi works
Project type and purpose
• Type: Monolithic Python-based system administration toolkit with both CLI (main.py) and GUI (gui.py) front ends.
• Purpose: Automate diagnostics, backups, and obsolescence audits for NordTransit Logistics’ IT infrastructure.
File structure
• Top-level entry points: main.py (CLI launcher), gui.py (GUI launcher)
• modules/ folder: three domain modules—diagnostic.py, backup.py, audit.py
• utils/ folder: shared services—logger.py (logging), output.py (JSON/console formatting)
• config/config.json: runtime parameters (credentials, targets, thresholds)
• data/eol_database.json: local reference data for end-of-life checks
• output/ (implied by README): subdirs backups/, reports/, logs/ for persisting results
• requirements.txt: Python dependencies (e.g., paramiko for SSH, PyMySQL, PySimpleGUI?)
• package.json / pnpm-lock.yaml: likely for packaging or bundling GUI assets (if any JS/CSS)
README for additional insights
• Three major functional modules (Diagnostic, Backup, Audit) each performing external interactions
• Dual interface: synchronous CLI menu vs. asynchronous GUI
• Outputs: console prints + JSON files + daily log files
• External dependencies: Windows hosts (WMI/PowerShell), Linux hosts (SSH), MySQL database, network scan for OS detection
Essential details to capture
• Configuration precedence: environment variables override config.json.
• Utilities are singletons/services shared by all modules.
• Output directory structure: separate folders for logs, reports, and backups.
• Data/eol_database.json as a read-only reference data store used by the Audit module.
• Error‐handling paths (e.g., Logger logs failures, modules return status codes).