upskill-event-manager/wordpress-dev/bin/obsolete
bengizmo d6211ee364 feat(testing): Implement HVAC_Test_User_Factory and update .gitignore
- Add HVAC_Test_User_Factory class with:
  * User creation with specific roles
  * Multiple role support
  * Persona management system
  * Account cleanup integration
- Create comprehensive test suite in HVAC_Test_User_Factory_Test.php
- Update testing improvement plan documentation
- Add implementation decisions to project memory bank
- Restructure .gitignore with:
  * Whitelist approach for better file management
  * Explicit backup exclusions
  * Specific bin directory inclusions

Part of the Account Management component from the testing framework improvement plan.
2025-04-14 17:41:36 -03:00
..
README.md feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
setup-dev.sh feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
sync-and-setup.sh feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00
verify-with-wpcli.sh feat(dev-env): implement backup-based development workflow 2025-03-26 11:26:18 -03:00

Obsolete Scripts

This directory contains scripts that have been replaced by newer versions or are no longer needed in the current development workflow.

Scripts in this Directory

  1. setup-dev.sh - Replaced by setup-from-backup.sh

    • The new script uses existing backups instead of trying to set up a fresh environment
    • This provides a more consistent development experience
  2. sync-production-temp.sh - Temporary script that was used during development

    • Replaced by sync-production.sh
  3. sync-and-setup.sh - Combined script that has been replaced by separate scripts

    • For syncing: use sync-production.sh
    • For setup: use setup-from-backup.sh
  4. verify-with-wpcli.sh - Script that used WP-CLI for verification

    • Replaced by verify-simple.sh and verify-dev.sh which don't require WP-CLI

Migration to New Workflow

The development workflow has been updated to use a backup-based approach:

  1. Create a backup from production (if needed): ./bin/sync-production.sh
  2. Set up the development environment from the backup: ./bin/setup-from-backup.sh
  3. Verify the environment: ./bin/verify-dev.sh or ./bin/verify-simple.sh

This approach is more reliable and consistent than the previous workflow.

Why These Scripts Are Kept

These scripts are kept for reference purposes and to maintain backward compatibility with any existing documentation or workflows that might still reference them.

If you need to use any of these scripts, please consider migrating to the new workflow instead.

Last Updated: March 26, 2025