ben/upskill-event-manager
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2
upskill-event-manager/wordpress-dev/bin/obsolete/README.md
bengizmo d1509b3d60 feat(dev-env): implement backup-based development workflow 
This commit introduces a more reliable and consistent approach to setting up
the development environment using backups:

- Add setup-from-backup.sh script for environment setup from existing backups
- Standardize script naming and organization
- Move obsolete scripts to bin/obsolete directory
- Update documentation with new workflow instructions
- Create migration guide for transitioning to new workflow
- Update Memory Bank with workflow improvements

The new workflow provides:
- More reliable environment setup
- Faster setup process
- Offline development capability
- Consistent development environments across team members

Breaking changes:
- setup-dev.sh is replaced by setup-from-backup.sh
- sync-and-setup.sh is replaced by separate scripts
- verify-with-wpcli.sh is no longer used

Migration path is documented in MIGRATION_GUIDE.md
2025-03-26 11:26:18 -03:00

1.5 KiB
Raw Blame History

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