- Document workflow for servers without git installed
- Explain that cache files are never in download archives
- Provide --clear-cache command for in-place updates
- Makes cache management clear for non-git deployments
- Add 'Fresh Deployment' section with git clean -fd command
- Update 'After Git Pull' section to include git clean for safety
- Clarify that 'total entries' in cache is line count, not WordPress count
- Helps users avoid confusion with stale cache on fresh deployments
DOCUMENTATION:
- CACHE_MANAGEMENT.md: Complete cache management guide
- Explains what gets cached and why
- Shows how to clear stale cache
- Provides troubleshooting for cache issues
- Best practices for cache management
CACHE COMMANDS:
- bash launcher.sh --clear-cache (clear stale data)
- bash launcher.sh --detect-only (verify fresh detection)
CACHE LIFECYCLE:
- First run: Builds cache from scratch
- Subsequent runs: Uses cached data (fast)
- After 1 hour: Cache auto-expires
- On pull: Clear cache for fresh data
SOLVES USER ISSUE:
- Old WordPress site count (29 entries)
- Stale domain/user listings
- Data not refreshing after system changes
- Cache files no longer committed to git
Developer