uprightbass360
b3019eb603
directory staging
2025-11-23 13:05:08 -05:00
uprightbass360
6ddfe9b2c7
cleanup: validation and integrations for importing data
2025-11-22 16:56:02 -05:00
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
uprightbass360
1948b0b3d4
Add comprehensive backup statistics and configurable intervals
...
• Enhanced backup-scheduler.sh with detailed performance metrics:
- Per-database timing and compression statistics
- Overall backup throughput and duration tracking
- Performance warnings for slow backups (>30min/>1hr)
- Completion markers to prevent incomplete backup copies
• Added BACKUP_INTERVAL_MINUTES configuration (default 60):
- Replaces fixed hourly scheduling with flexible intervals
- Supports any interval from 1 minute to hours
- Maintains daily backup scheduling at configured time
• New verify-backup-complete.sh script:
- Checks backup completion before copying/processing
- Supports waiting with timeout for active backups
- Backward compatible with manifest validation
• Enhanced backup manifests with performance data:
- Duration, compression ratio, throughput metrics
- Enables historical performance trend analysis
- Portable implementation using awk instead of bc
Tested with 5-minute intervals over 18+ hours:
- 218 successful backups, 0 failures
- Consistent 82.1% compression, 52MB/s throughput
- Production-ready backup monitoring infrastructure
2025-11-13 17:18:54 -05:00
uprightbass360
e521f8bf10
make worldserver wait for clientdata
2025-11-10 03:18:44 -05:00
uprightbass360
68dc21d5ef
import enhancements and npc spawn sketches
2025-11-10 01:59:47 -05:00
uprightbass360
7000f35972
fix: backup permissions
2025-11-09 15:03:17 -05:00
uprightbass360
4bf781b82f
make backup run as container user
2025-11-09 05:49:51 -05:00
uprightbass360
90c53c47d9
bind network and remote cleanup
2025-11-09 05:15:58 -05:00
uprightbass360
a18e315f1f
refactor: reorganize scripts under bash/python
2025-11-09 02:49:26 -05:00
uprightbass360
7813414f2c
Improve client data container: add 7z, root access, and ownership fix
...
- Run container as root during extraction to avoid permission issues
- Install p7zip-full for faster 7z extraction vs unzip
- Fix file ownership after extraction using chown
- Remove problematic retry logic that was causing corruption issues
- Keep reliable original script with version detection and caching
2025-11-08 14:39:39 -05:00
uprightbass360
622fd518d2
Introduce dynamic overrides and rename module manifest
2025-11-08 01:50:30 -05:00
uprightbass360
d99dad025a
feat: add mysql exposure toggle and client data bind
2025-11-07 22:29:13 -05:00
uprightbass360
18b053aa02
Refactor module staging to use manifest/env defaults and tag build images from .env
2025-11-02 03:17:13 -05:00
uprightbass360
d59c785f11
adding automatic module inclusion features and bugfixes
2025-11-01 00:13:34 -04:00
uprightbass360
d8413f59e1
fix: permissions
2025-10-29 18:40:05 -04:00
uprightbass360
28cfb6f5e1
fix: permissions
2025-10-29 17:50:18 -04:00
uprightbass360
86e2f7ad4f
fixing root containers
2025-10-29 17:33:13 -04:00
uprightbass360
1fc7ee88a6
fix: updates clientdata job to use non-root
2025-10-29 12:20:47 -04:00
uprightbass360
cf8229d1c6
feat: local paths/users
2025-10-29 01:35:09 -04:00
uprightbass360
39ac59d641
automation tweaks
2025-10-26 19:12:56 -04:00
uprightbass360
f46b88bd93
variable cleanup
2025-10-26 04:49:25 -04:00
uprightbass360
d8696d2ab4
cleanup: Update paths and builds
2025-10-24 22:49:44 -04:00
uprightbass360
fdd23c7fb7
Improve database timeout handling and add local testing setup
...
- Update database timeout values for better Portainer/NFS compatibility
- Add .env-database-local for local testing with reduced resource requirements
- Create local data directories and backup script validation
- Split compose validation confirms proper service dependency configuration
- Increase MySQL health check timeouts: start_period 60s→120s, timeout 10s→15s
- Extend database wait times: retries 30→60, sleep 5→10 (total 150s→600s)
🤖 Generated with [Claude Code](https://claude.com/claude-code )
2025-09-29 21:14:46 -04:00
Deckard
7325c3347f
Fix MySQL NFS permission issues
...
- Run MySQL container as root (user: 0:0) to handle NFS mount permissions
- Add --user=mysql flag to MySQL command to switch to mysql user after initialization
- This resolves 'Permission denied' errors when using NFS volumes for MySQL data
2025-09-27 16:30:55 -04:00
Deckard
12090955c6
Fix client data download to use data.zip instead of data.7z
...
- Update GitHub API search to look for .zip files instead of .7z
- Change fallback URL to use correct data.zip filename
- Update extraction to use unzip instead of 7z command
- This fixes the 404 error and invalid archive issues
2025-09-27 16:20:39 -04:00
Deckard
15ddf7aa99
Remove obsolete version attribute to fix Docker Compose warnings
2025-09-27 16:10:17 -04:00
Deckard
a22f65a387
Simplify volume path syntax to fix path duplication
...
- Replace complex conditional syntax with simple default pattern
- Remove 4x variable references that caused /nfs/containers duplication
- Use ./volumes/azerothcore/* for local development
- Use /nfs/containers/azerothcore/* for Portainer deployment
- Remove unused named volumes section
2025-09-27 15:46:10 -04:00
Deckard
10713b677a
Fix volume path configuration for Portainer NFS deployment
...
- Fix client data volume to use consistent STORAGE_PATH_CONTAINERS pattern
- Add missing ac_data volume definition for local development fallback
- Ensures files go to /nfs/containers/azerothcore/data instead of nested paths
2025-09-27 14:57:53 -04:00
Deckard
6787cf863e
Fix all command syntax issues for Portainer compatibility
...
- Convert MySQL command args from folded scalar to array format
- Convert multiline script commands to Portainer-compatible syntax
- Remove nested quoted strings that cause YAML parsing errors
2025-09-27 03:28:09 -04:00
Deckard
6d15bcef6f
Fix ac-client-data command syntax for Portainer compatibility
2025-09-27 03:22:50 -04:00
Deckard
a0cc5cc79a
Fix YAML smart quotes causing Portainer deployment error
...
Replace smart quotes with standard quotes in client-data download script
to resolve 'top-level object must be a mapping' error in Portainer
2025-09-27 03:12:18 -04:00
Deckard
d03eed0b06
Simplify compose files: rename unified to docker-compose.yml and remove portainer-stack.yml
...
- Rename acore-unified.yml to standard docker-compose.yml for easier usage
- Remove portainer-stack.yml as functionality is now unified in main compose file
- Standardizes on single compose file for both local and Portainer deployment
2025-09-27 03:03:36 -04:00