3d6bab9661a477ee2feafd53e61481222376a92b
4 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
 cschantz
|
3d6bab9661 |
Add deployment documentation and automated deploy script
Make it dead simple to deploy and run validation scripts on test servers. NEW FILES: 1. testing/DEPLOYMENT.md - Complete deployment guide with 5 different methods - SCP (simplest), GitHub clone, wget/curl, copy-paste, archive - Step-by-step instructions for both InterWorx and Plesk - What to expect during execution - How to review and share results - Troubleshooting section - Security notes (scripts are read-only, safe to run) 2. testing/deploy-and-run.sh (AUTOMATED!) - One command to deploy, run, and retrieve results - Handles all 4 steps automatically - Shows live summary of pass/fail/warn counts - Extracts critical answers automatically - Error handling and helpful tips USAGE: Simple method (manual): ```bash scp testing/validate-interworx.sh root@SERVER:/tmp/ ssh root@SERVER "/tmp/validate-interworx.sh" scp root@SERVER:/tmp/interworx-validation-results.txt ./ ``` Automated method (one command!): ```bash cd testing/ ./deploy-and-run.sh 192.168.1.100 interworx # OR ./deploy-and-run.sh plesk-server.com plesk ``` WHAT THE AUTOMATED SCRIPT DOES: [1/4] Deploys script to server via SCP [2/4] Runs validation script remotely [3/4] Retrieves results file [4/4] Shows summary (PASS/FAIL/WARN counts + critical answers) OUTPUT EXAMPLE: ``` ======================================================================= VALIDATION SUMMARY ======================================================================= PASS: 45 FAIL: 0 WARN: 3 ✓ All critical tests passed! ======================================================================= CRITICAL ANSWERS FOUND ======================================================================= Document roots: /home/USERNAME/DOMAIN/html/ Access logs: /home/USERNAME/var/DOMAIN/logs/access_log Database prefix: username_ (VERIFIED) Cron user: testuser ``` SECURITY: - Scripts are read-only (don't modify system) - Only exception: cron test (writes then immediately deletes) - Results in /tmp/ (auto-cleaned on reboot) - No passwords logged Ready to deploy to test servers! 🚀 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> |
||
|
cschantz
|
36eda044c2 |
Add directory tree visualization to validation scripts
Added smart, targeted directory trees for critical paths only. NEW TESTS: Plesk validator - TEST 14: Directory Structure Visualization • Domain structure: /var/www/vhosts/DOMAIN/ (depth 3) • Log structure: /var/www/vhosts/system/DOMAIN/ (depth 2) • General vhosts overview with sample domain • Plesk system directories: /usr/local/psa/ • PHP directories: /opt/plesk/php/ InterWorx validator - TEST 12: Directory Structure Visualization • User structure: /home/USERNAME/ (depth 2) • Domain structure: /home/USERNAME/DOMAIN/ (depth 3) • Log structure: /home/USERNAME/var/DOMAIN/ (depth 2) • General /home overview • InterWorx system directories: /usr/local/interworx/ • Apache config directory: /etc/httpd/conf.d/ FEATURES: • Uses 'tree' command if available (pretty output) • Falls back to find-based tree if tree not installed • Limited depth (2-3 levels max) to avoid overwhelming output • Shows actual log files with sizes • Documents sample vhost config locations WHY THIS HELPS: • Visual understanding of how each panel organizes files • See EXACTLY where logs/domains/configs live • Understand directory naming conventions • Verify our assumptions about path structures • Creates reference documentation for future work EXAMPLE OUTPUT: ``` === DOMAIN DIRECTORY STRUCTURE: example.com === /home/testuser/example.com/ ├── html/ │ ├── wp-admin/ │ ├── wp-content/ │ └── wp-config.php ├── cgi-bin/ └── ssl/ === LOG DIRECTORY STRUCTURE === /home/testuser/var/example.com/logs/ ├── access_log (2.3M) ├── error_log (145K) └── transfer.log (890K) ``` This visual context will be invaluable for understanding each panel's layout! 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> |
||
|
cschantz
|
a85ca92fd4 |
MAJOR ENHANCEMENT: Validation scripts now test OPERATIONS and document EVERYTHING
These scripts are now comprehensive discovery tools that:
1. Actually TEST operations (not just detect)
2. Document complete system knowledge for future reference
CRITICAL NEW TESTS:
Plesk validator (validate-plesk.sh):
• NEW TEST 8: File ownership detection + cron user determination
- Checks who owns document root files
- Determines correct user for cron jobs
- ANSWERS: Should we use www-data, owner, or domain-specific user?
• ENHANCED TEST 9: Cron system operational testing
- Actually WRITES test cron entry (then removes it)
- Tests both standard crontab AND plesk bin cron
- ANSWERS: Which cron system actually works?
• NEW TEST 13: WordPress file permissions & wp-config.php access
- Tests if we can read wp-config.php
- Extracts database credentials
- Determines database prefix pattern from REAL data
• NEW TEST 14: Comprehensive system documentation
- Catalogs ALL Plesk bin commands
- Lists ALL domains on system
- Documents ALL PHP versions
- Records web server config (nginx + Apache detection)
- Creates "QUICK REFERENCE FOR DEVELOPERS" section
InterWorx validator (validate-interworx.sh):
• NEW TEST 11: WordPress file permissions & cron user testing
- Extracts database name from wp-config.php
- VERIFIES username_ database prefix from real data
- Actually WRITES test cron entry (then removes it)
- ANSWERS: Can we use crontab -u USER for cron jobs?
• NEW TEST 12: Comprehensive system documentation
- Catalogs ALL InterWorx bin commands
- Lists ALL users on system
- Lists ALL vhost configurations
- Documents sample vhost config structure
- Creates "QUICK REFERENCE FOR DEVELOPERS" section
WHAT THESE SCRIPTS NOW ANSWER:
Plesk - CRITICAL BLOCKERS:
✓ Who owns web files? (determines cron user)
✓ Can we write crontab entries?
✓ What's the database prefix pattern? (from real wp-config.php)
✓ Which cron system to use?
✓ All available Plesk commands
✓ Complete system inventory
InterWorx - VERIFICATION:
✓ Confirms username_ database prefix (from real data)
✓ Confirms crontab -u USER works
✓ Documents all InterWorx commands
✓ Complete system inventory
OUTPUT FORMAT:
Both scripts now generate comprehensive results files with:
- Color-coded test results (PASS/FAIL/WARN)
- Complete system documentation
- Quick reference guide for developers
- Actionable answers to critical questions
These scripts will learn EVERYTHING we need to know in one run!
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
|
||
|
cschantz
|
20a3615242 |
TESTING PHASE: Add comprehensive validation scripts for InterWorx and Plesk
Created automated validation framework to test multi-panel refactoring on real servers. NEW FILES: - testing/validate-interworx.sh (650+ lines) - 10 comprehensive tests validating all InterWorx assumptions - File system structure, logs, domain lookups, database prefix - WordPress detection, cron system, PHP config, CLI tools - Color-coded output + detailed results file - testing/validate-plesk.sh (750+ lines) - 12 comprehensive tests validating all Plesk assumptions - File system structure, logs, plesk bin commands - Domain/user lookups, database prefix, system user detection - WordPress detection, cron system, PHP config - Critical: Determines system user for cron jobs - testing/README.md - Complete testing guide and documentation - Quick start instructions for both panels - What gets validated and why - 4-phase testing priority plan - Known issues and next steps UPDATED: - REFDB_FORMAT.txt - Added TESTING & VALIDATION PHASE section - Documented validation scripts and their coverage - Listed testing priority and next actions - Updated last modified date VALIDATION COVERAGE: InterWorx (10 tests): ✅ All file paths (verified from official docs) ✅ Database prefix: username_ (verified) ⏳ Domain→User lookup (needs real server) ⏳ User→Domains lookup (needs real server) ⏳ WordPress detection (needs real server) Plesk (12 tests): ⏳ File paths (assumed correct) ❓ Database prefix (appears to be no prefix) ❓ System user for cron (critical for wordpress-cron-manager!) ❓ Cron system (standard vs plesk bin cron) ⏳ All lookup methods (need real server) READY FOR: Testing on real InterWorx and Plesk servers 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> |