# Framework Migration Guides

**Last Updated:** 2026-01-31  
**Document Version:** 1.0  
**Status:** Active Documentation

---

**Date:** 2026-01-22  
**Purpose:** Guide migration from individual scripts to unified frameworks

---

## Overview

Five unified frameworks have been created to consolidate 378+ scripts:
- `verify-all.sh` - Consolidates 124 verify/check/validate scripts
- `list.sh` - Consolidates 18 list/show/get scripts
- `fix-all.sh` - Consolidates 93 fix-*.sh scripts
- `configure.sh` - Consolidates 41 configure/config scripts
- `deploy.sh` - Consolidates 102 deploy/setup/install scripts

---

## 1. verify-all.sh Migration Guide

### Old Way
```bash
./scripts/check-container-services.sh 5000
./scripts/verify-blockscout-port-4000.sh
./scripts/validate-deployment-ml110.sh
```

### New Way
```bash
./scripts/verify-all.sh container 5000
./scripts/verify-all.sh blockscout health
./scripts/verify-all.sh all status
```

### Migration Mapping
- `check-*.sh` → `verify-all.sh [component] status`
- `verify-*.sh` → `verify-all.sh [component] [type]`
- `validate-*.sh` → `verify-all.sh [component] config`

---

## 2. list.sh Migration Guide

### Old Way
```bash
./scripts/list-all-vmids-complete.sh
./scripts/list-r630-01-vms.sh
./scripts/show-container-status.sh
```

### New Way
```bash
./scripts/list.sh containers
./scripts/list.sh vms r630-01
./scripts/list.sh containers running
```

### Migration Mapping
- `list-*.sh` → `list.sh [type] [filter]`
- `show-*.sh` → `list.sh [type] [filter]`
- `get-*.sh` → `list.sh [type] [filter]`

---

## 3. fix-all.sh Migration Guide

### Old Way
```bash
./scripts/fix-all-blockscout-issues.sh
./scripts/fix-redis-and-start.sh
./scripts/fix-nginx-blockscout-config.sh
```

### New Way
```bash
./scripts/fix-all.sh blockscout all
./scripts/fix-all.sh service redis 10120
./scripts/fix-all.sh nginx blockscout --dry-run
```

### Migration Mapping
- `fix-*-service.sh` → `fix-all.sh service [service-name]`
- `fix-*-network.sh` → `fix-all.sh network [vmid]`
- `fix-*-config.sh` → `fix-all.sh config [file]`

---

## 4. configure.sh Migration Guide

### Old Way
```bash
./scripts/configure-container-networks.sh
./scripts/configure-nginx-jwt-auth-simple.sh
./scripts/configure-service-dependencies.sh
```

### New Way
```bash
./scripts/configure.sh network setup
./scripts/configure.sh nginx setup
./scripts/configure.sh service dependencies setup
```

### Migration Mapping
- `configure-*.sh` → `configure.sh [component] [action]`
- `config-*.sh` → `configure.sh [component] [action]`

---

## 5. deploy.sh Migration Guide

### Old Way
```bash
./scripts/deploy-to-proxmox-host.sh
./scripts/setup-thirdweb-rpc-nodes.sh
./scripts/install-services-via-enter.sh
```

### New Way
```bash
./scripts/deploy.sh infrastructure all
./scripts/deploy.sh rpc thirdweb
./scripts/deploy.sh service postgresql
```

### Migration Mapping
- `deploy-*.sh` → `deploy.sh [component] [options]`
- `setup-*.sh` → `deploy.sh [component] setup`
- `install-*.sh` → `deploy.sh [component] install`

---

## Migration Process

1. **Identify Script Type** - Determine which framework it belongs to
2. **Map Parameters** - Map old script parameters to framework parameters
3. **Test Framework** - Test framework with equivalent parameters
4. **Archive Original** - Move original script to archive/consolidated/
5. **Update References** - Update any documentation or automation

---

## Automated Migration

Use the migration script:
```bash
# Dry run
./scripts/migrate-to-frameworks.sh all --dry-run

# Execute migration
./scripts/migrate-to-frameworks.sh all --execute
```

---

**Status:** Migration guides created, ready for script migration