dandri/meshcore-analyzer
1
0
Fork 0
mirror of https://github.com/Kpa-clawbot/meshcore-analyzer.git synced 2026-05-29 14:44:12 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: simplify backup/update sections — use manage.sh, drop volume inspect

Browse Source 
Backup section now shows manage.sh commands instead of raw docker
volume inspect paths. Update section is one command.
This commit is contained in:
you
2026-03-25 00:46:04 +00:00
parent efe947bb62
commit 35675b0898
1 changed files with 13 additions and 40 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/DEPLOYMENT.md
+13 -40
View File
@@ -326,63 +326,36 @@ Don't expose 1883 at all. Instead, have your observers publish to a shared publi
## Database Backups
Packet data is stored in `meshcore.db` inside the `meshcore-data` Docker volume.
Packet data is stored in `meshcore.db` inside the data volume.
### Find the database file
**Using manage.sh (easiest):**
```bash
docker volume inspect meshcore-data --format '{{ .Mountpoint }}'
# Prints something like: /var/lib/docker/volumes/meshcore-data/_data
./manage.sh backup # Saves to ./backups/meshcore-TIMESTAMP.db
./manage.sh backup ~/my-backup.db # Custom path
./manage.sh restore ./backups/some-file.db # Restore (backs up current DB first)
```
The database is at that path + `/meshcore.db`.
**Local directory mount (recommended):**
### Manual backup
If you used `-v ./analyzer-data:/app/data` instead of a Docker volume, the database is just `./analyzer-data/meshcore.db` — back it up however you like.
```bash
cp $(docker volume inspect meshcore-data --format '{{ .Mountpoint }}')/meshcore.db \
~/meshcore-backup-$(date +%Y%m%d).db
```
### Automated daily backup (cron)
**Automated daily backup (cron):**
```bash
crontab -e
# Add this line:
0 3 * * * cp $(docker volume inspect meshcore-data --format '\{\{ .Mountpoint \}\}')/meshcore.db /home/youruser/backups/meshcore-$(date +\%Y\%m\%d).db
```
### Easier alternative: use a local directory
Instead of a Docker volume, mount a local directory. Replace `-v meshcore-data:/app/data` with:
```bash
-v ./analyzer-data:/app/data
```
Now the database is just `./analyzer-data/meshcore.db` — easy to find, back up, and restore.
### Restoring from backup
Stop the container, replace `meshcore.db` with your backup file, start the container:
```bash
docker stop meshcore-analyzer
cp ~/meshcore-backup-20260324.db $(docker volume inspect meshcore-data --format '{{ .Mountpoint }}')/meshcore.db
docker start meshcore-analyzer
# Add:
0 3 * * * cd /path/to/meshcore-analyzer && ./manage.sh backup
```
## Updating
```bash
cd meshcore-analyzer
git pull
docker build -t meshcore-analyzer .
docker stop meshcore-analyzer
docker rm meshcore-analyzer
# Re-run the same docker run command from Quick Start step 4
./manage.sh update
```
Pulls latest code, rebuilds the image, restarts the container. Data is preserved.
Data is preserved in the Docker volumes.
**Tip:** Save your `docker run` command in a script (`run.sh`) so you don't have to remember all the flags.