Files
AzerothCore-RealmMaster/status.sh
uprightbass360 e6231bb4a4 feat: comprehensive module system and database management improvements
This commit introduces major enhancements to the module installation system,
database management, and configuration handling for AzerothCore deployments.

## Module System Improvements

### Module SQL Staging & Installation
- Refactor module SQL staging to properly handle AzerothCore's sql/ directory structure
- Fix SQL staging path to use correct AzerothCore format (sql/custom/db_*/*)
- Implement conditional module database importing based on enabled modules
- Add support for both cpp-modules and lua-scripts module types
- Handle rsync exit code 23 (permission warnings) gracefully during deployment

### Module Manifest & Automation
- Add automated module manifest generation via GitHub Actions workflow
- Implement Python-based module manifest updater with comprehensive validation
- Add module dependency tracking and SQL file discovery
- Support for blocked modules and module metadata management

## Database Management Enhancements

### Database Import System
- Add db-guard container for continuous database health monitoring and verification
- Implement conditional database import that skips when databases are current
- Add backup restoration and SQL staging coordination
- Support for Playerbots database (4th database) in all import operations
- Add comprehensive database health checking and status reporting

### Database Configuration
- Implement 10 new dbimport.conf settings from environment variables:
  - Database.Reconnect.Seconds/Attempts for connection reliability
  - Updates.AllowedModules for module auto-update control
  - Updates.Redundancy for data integrity checks
  - Worker/Synch thread settings for all three core databases
- Auto-apply dbimport.conf settings via auto-post-install.sh
- Add environment variable injection for db-import and db-guard containers

### Backup & Recovery
- Fix backup scheduler to prevent immediate execution on container startup
- Add backup status monitoring script with detailed reporting
- Implement backup import/export utilities
- Add database verification scripts for SQL update tracking

## User Import Directory

- Add new import/ directory for user-provided database files and configurations
- Support for custom SQL files, configuration overrides, and example templates
- Automatic import of user-provided databases and configs during initialization
- Documentation and examples for custom database imports

## Configuration & Environment

- Eliminate CLIENT_DATA_VERSION warning by adding default value syntax
- Improve CLIENT_DATA_VERSION documentation in .env.template
- Add comprehensive database import settings to .env and .env.template
- Update setup.sh to handle new configuration variables with proper defaults

## Monitoring & Debugging

- Add status dashboard with Go-based terminal UI (statusdash.go)
- Implement JSON status output (statusjson.sh) for programmatic access
- Add comprehensive database health check script
- Add repair-storage-permissions.sh utility for permission issues

## Testing & Documentation

- Add Phase 1 integration test suite for module installation verification
- Add comprehensive documentation for:
  - Database management (DATABASE_MANAGEMENT.md)
  - Module SQL analysis (AZEROTHCORE_MODULE_SQL_ANALYSIS.md)
  - Implementation mapping (IMPLEMENTATION_MAP.md)
  - SQL staging comparison and path coverage
  - Module assets and DBC file requirements
- Update SCRIPTS.md, ADVANCED.md, and troubleshooting documentation
- Update references from database-import/ to import/ directory

## Breaking Changes

- Renamed database-import/ directory to import/ for clarity
- Module SQL files now staged to AzerothCore-compatible paths
- db-guard container now required for proper database lifecycle management

## Bug Fixes

- Fix module SQL staging directory structure for AzerothCore compatibility
- Handle rsync exit code 23 gracefully during deployments
- Prevent backup from running immediately on container startup
- Correct SQL staging paths for proper module installation
2025-11-22 16:56:02 -05:00

80 lines
1.5 KiB
Bash
Executable File

#!/bin/bash
# Wrapper that ensures the statusdash TUI is built before running.
set -euo pipefail
SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
PROJECT_DIR="$SCRIPT_DIR"
BINARY_PATH="$PROJECT_DIR/statusdash"
SOURCE_DIR="$PROJECT_DIR/scripts/go"
CACHE_DIR="$PROJECT_DIR/.gocache"
usage() {
cat <<EOF
statusdash wrapper
Usage: $0 [options] [-- statusdash-args]
Options:
--rebuild Force rebuilding the statusdash binary
-h, --help Show this help text
All arguments after '--' are passed directly to the statusdash binary.
Go must be installed locally to build statusdash (https://go.dev/doc/install).
EOF
}
force_rebuild=0
statusdash_args=()
while [[ $# -gt 0 ]]; do
case "$1" in
--rebuild)
force_rebuild=1
shift
;;
-h|--help)
usage
exit 0
;;
--)
shift
statusdash_args+=("$@")
break
;;
*)
statusdash_args+=("$1")
shift
;;
esac
done
ensure_go() {
if ! command -v go >/dev/null 2>&1; then
cat >&2 <<'ERR'
Go toolchain not found.
statusdash requires Go to build. Install Go from https://go.dev/doc/install and retry.
ERR
exit 1
fi
}
build_statusdash() {
ensure_go
mkdir -p "$CACHE_DIR"
echo "Building statusdash..."
(
cd "$SOURCE_DIR"
GOCACHE="$CACHE_DIR" go build -o "$BINARY_PATH" .
)
}
if [[ $force_rebuild -eq 1 ]]; then
rm -f "$BINARY_PATH"
fi
if [[ ! -x "$BINARY_PATH" ]]; then
build_statusdash
fi
exec "$BINARY_PATH" "${statusdash_args[@]}"