zitinexus-public
/
zitinexus-router-script
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
zitinexus-router-script/UI/test
History
Edmund Tan 2617475c0c fixed script new8 2025-07-23 00:44:16 +08:00
..
CLOUDSTACK_FIXES.md fixed script new8 2025-07-23 00:44:16 +08:00
README.md fixed script new8 2025-07-23 00:44:16 +08:00
debug-command-execution-public.php fixed script new8 2025-07-23 00:44:16 +08:00
debug-command-execution.php fixed script new8 2025-07-23 00:44:16 +08:00
debug-paths.php fixed script new8 2025-07-23 00:44:16 +08:00
fix-permissions.sh fixed script new8 2025-07-23 00:44:16 +08:00
pre-enrollment-check.php fixed script new8 2025-07-23 00:44:16 +08:00
quick-fix-cloudstack.sh fixed script new8 2025-07-23 00:44:16 +08:00
test-assets.php fixed script new8 2025-07-23 00:44:16 +08:00
test-php-detection.sh fixed script new8 2025-07-23 00:44:16 +08:00
troubleshoot.sh fixed script new8 2025-07-23 00:44:16 +08:00

README.md

Test and Debug Files

This directory contains all testing, debugging, and development utility files for the ZitiNexus Router Enrollment UI.

📁 Files in This Directory

Debug Files:

  • debug-command-execution.php - Debug script for testing command execution
  • debug-command-execution-public.php - Public version of debug script
  • debug-paths.php - Debug script for testing file paths and includes

Test Files:

  • test-assets.php - Test script for asset loading and paths
  • test-php-detection.sh - Shell script for testing PHP detection

🎯 Purpose

This directory serves as a container for:

  • Development utilities that help during coding
  • Debug scripts for troubleshooting issues
  • Test files for validating functionality
  • Temporary files created during development

🚫 Important Notes

  • These files are NOT part of the production system
  • Never reference these files from production code
  • These files may be removed or modified without notice
  • Do not rely on these files for production functionality

🔧 Usage Guidelines

When Creating Test Files:

  1. Always place them in this directory
  2. Use descriptive names (e.g., test-enrollment-flow.php)
  3. Include comments explaining the test purpose
  4. Clean up when no longer needed

When Debugging:

  1. Create debug files here, not in main directories
  2. Use temporary names that won't conflict
  3. Remove debug files after issue is resolved
  4. Document any permanent debug utilities

📋 File Descriptions

debug-command-execution.php

  • Tests command execution functionality
  • Validates sudo permissions
  • Checks system command availability

debug-paths.php

  • Tests include paths and file references
  • Validates asset loading
  • Checks directory permissions

test-assets.php

  • Tests CSS and JavaScript loading
  • Validates asset paths from different locations
  • Checks for missing assets

test-php-detection.sh

  • Shell script for testing PHP installation
  • Validates PHP version and modules
  • Tests web server configuration

🧹 Maintenance

This directory should be cleaned regularly:

  • Remove obsolete test files
  • Archive useful debug scripts
  • Update documentation as needed
  • Keep only actively used utilities

⚠️ Security Note

Some files in this directory may contain:

  • Debug output that reveals system information
  • Test credentials or keys
  • Sensitive configuration details

Never deploy this directory to production servers.