 cschantz
|
3250e8e32d
|
COMPREHENSIVE INTERWORX COMPATIBILITY AUDIT
Created detailed audit report of ALL 38 toolkit modules.
FINDINGS:
- ✅ 3 modules already InterWorx compatible
- ⚠️ 14 modules need InterWorx fixes
- ✓ 21 modules are control panel agnostic
CRITICAL ISSUES IDENTIFIED:
1. Security Modules (Priority 1)
- live-attack-monitor.sh: Hardcoded domlogs path
- malware-scanner.sh: Hardcoded public_html, cPanel paths
- optimize-ct-limit.sh: Wrong fallback path
2. Website Diagnostics (Priority 2)
- website-error-analyzer.sh: Heavy cPanel dependencies
- 500-error-tracker.sh: /var/cpanel/users/* lookups
3. Monitoring Tools (Priority 3)
- web-traffic-monitor.sh: Hardcoded domlogs
- tail-apache-access.sh: Hardcoded paths
- tail-apache-error.sh: Hardcoded paths
- network-bandwidth-analyzer.sh: Hardcoded log detection
KEY PATH DIFFERENCES DOCUMENTED:
- Access logs: /var/log/apache2/domlogs/domain → /home/user/var/domain/logs/access_log
- Document root: /home/user/public_html → /home/user/domain.com/html
- Error logs: Different per-domain structure
- User config: /var/cpanel/users/* → NodeWorx API/vhost configs
STANDARD FIX PATTERN DEFINED:
1. Use SYS_LOG_DIR from system-detect.sh
2. Use get_user_info()/get_user_domains() from user-manager.sh
3. Support both cPanel and InterWorx document root patterns
4. Add InterWorx-specific log discovery
IMPLEMENTATION PLAN:
- Phase 3: Critical security modules (3 modules)
- Phase 4: Website diagnostics (2 modules)
- Phase 5: Monitoring tools (4 modules)
- Phase 6: System health check (1 module)
Estimated effort: 8 hours for full InterWorx parity
REPORT LOCATION:
INTERWORX_COMPATIBILITY_AUDIT.md
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
|
2025-11-19 18:57:11 -05:00 |
|