nchebrov/AzerothCore-RealmMaster
1
0
Fork 0
mirror of https://github.com/uprightbass360/AzerothCore-RealmMaster.git synced 2026-01-13 09:07:20 +00:00
Code Issues Packages Projects Releases Wiki Activity

import enhancements and npc spawn sketches

Browse Source
This commit is contained in:
uprightbass360
2025-11-10 01:59:47 -05:00
parent fbf6b23f56
commit 68dc21d5ef
21 changed files with 1351 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
database-import/README.md
View File

@@ -2,9 +2,11 @@
Place your database backup files here for automatic import during deployment.
## Supported Files
## Supported Imports
- `.sql` files (uncompressed SQL dumps)
- `.sql.gz` files (gzip compressed SQL dumps)
- **Full backup directories** (e.g., `ExportBackup_YYYYMMDD_HHMMSS/` containing multiple dumps)
- **Full backup archives** (`.tar`, `.tar.gz`, `.tgz`, `.zip`) that contain the files above
## How to Use
@@ -13,6 +15,9 @@ Place your database backup files here for automatic import during deployment.
cp my_auth_backup.sql.gz ./database-import/
cp my_world_backup.sql.gz ./database-import/
cp my_characters_backup.sql.gz ./database-import/
# or drop an entire ExportBackup folder / archive
cp -r ExportBackup_20241029_120000 ./database-import/
cp ExportBackup_20241029_120000.tar.gz ./database-import/
```
2. **Run deployment:**
@@ -25,13 +30,15 @@ Place your database backup files here for automatic import during deployment.
## File Naming
- Any filename works - the system will auto-detect database type by content
- Recommended naming: `auth.sql.gz`, `world.sql.gz`, `characters.sql.gz`
- Full backups keep their original directory/archive name so you can track multiple copies
## What Happens
- Files from this folder are copied to `local-storage/backups/daily/`
- Database import system automatically restores them
- Original files remain here for reference
- Individual `.sql`/`.sql.gz` files are copied to `storage/backups/daily/` with a timestamped name
- Full backup directories or archives are staged in `storage/backups/ImportBackup/`
- Database import system automatically restores the most recent matching backup
- Original files remain here for reference (archives are left untouched)
## Notes
- Only processed on first deployment (when databases don't exist)
- Files are copied with timestamp to backup directory
- Empty folder is ignored - no files, no import
- Files/directories are copied once; existing restored databases will skip import
- Empty folder is ignored - no files, no import