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
14 lines
No EOL
742 B
Markdown
14 lines
No EOL
742 B
Markdown
# WordPress Development Environment Management Proposal
|
|
|
|
**Status**: Superseded by New Workflow
|
|
**Last Updated**: March 26, 2025
|
|
**Scope**: Development environment setup and management
|
|
|
|
> **Note**: This document has been superseded by the new backup-based workflow. Please refer to the following documents for the current approach:
|
|
> - [README.md](README.md) - Current development environment documentation
|
|
> - [MIGRATION_GUIDE.md](MIGRATION_GUIDE.md) - Guide for migrating to the new workflow
|
|
|
|
## Overview
|
|
This script manages the WordPress development environment for the Upskill HVAC Community Events project, providing functionality to check status, sync with production, and deploy test configurations.
|
|
|
|
[... original content follows ...] |