Jul 17: WP migration complete, Mattermost deployed, backup restore system, DNS updates

README.md

@@ -1,6 +1,6 @@
 # IT Pro Partner — Infrastructure Documentation
 
-> **Last Updated:** July 16, 2026
+> **Last Updated:** July 17, 2026
 > **Maintainer:** Sho'Nuff
 
 ---
@@ -42,8 +42,10 @@
   - Open WebUI (Docker, port 3000) — ai.itpropartner.com
   - n8n + Postgres (Docker, port 5678) — n8n.itpropartner.com
   - LiteLLM (Docker) + Postgres — admin-ai.itpropartner.com
+  - Mattermost Team Edition (Docker, port 8065) — noc.itpropartner.com
   - Caddy (systemd, 80/443)
   - 4 MCP servers: Browser (:8901), Filesystem (:8900), Email (:8902), Git (:8903)
+  - Super Search MCP (systemd, port 8899)
 
 ### App2 Server
 - **Hostname:** app2
@@ -65,12 +67,16 @@
 - **Provider:** netcup RS 4000 G12
 - **Specs:** 12 vCPU EPYC 9645, 32 GB DDR5 ECC, 1 TB NVMe
 - **OS:** Debian 13
-- **Role:** Web Hosting
+- **Role:** Web Hosting + Backup Restore
 - **Key Services:**
   - CloudPanel CE — panel.itpropartner.com
   - Nginx (80/443) + Percona MySQL 8.4 + PHP 8.3
-  - voipsimplicity.com (WordPress, migrated Jul 16)
-  - my.voipsimplicity.com (static HTML SPA, VoIP customer portal)
+  - Backup Restore System (Flask, port 8090) — my.itpropartner.com/backups
+  - WordPress sites (7 migrated from wphost02, all live):
+    - debtreecoveryexperts.com, boxpilotlogistics.com, iamgmb.com
+    - katiewattsdesign.com, vigilanttac.com, apextrackexperience.com
+    - mainwp.itpropartner.com, voipsimplicity.com, my.voipsimplicity.com
+  - Daily snapshots: 1 AM + 1 PM, 60-day retention, /opt/backup-restore/snapshots
 
 ### Core-BU (Warm Standby)
 - **Hostname:** core-bu
@@ -249,3 +255,5 @@ All SSL certificates issued via Let's Encrypt through Caddy. All certs auto-rene
 - **Provider diversity:** core-bu stays at Hetzner specifically so a netcup outage can't kill both Core and standby simultaneously.
 - **app3 MySQL:** Root password at `MOQMINFQIhklM0AF`, accessible via 127.0.0.1:3306.
 - **CloudPanel:** SQLite DB at `/home/clp/htdocs/app/data/db.sq3` — users live here, not in MySQL.
+- **AWS CLI PATH:** All backup scripts must use `/opt/awscli-venv/bin/aws` or `source /opt/awscli-venv/bin/activate` — `aws` bare fails in cron context (PATH doesn't include venv bin). Documented in server-provisioning-standard v1.3.0.
+- **Backup verification:** Always run at least one manual backup after provisioning a server and verify it landed in S3 — never trust cron entries alone. Silent failures (`aws: command not found`, wrong file paths, S3 permission issues) won't surface otherwise.