🚀 MeshMonitor 3.0.0-beta5
This beta release adds multi-database support with PostgreSQL and MySQL/MariaDB as optional backends, plus a complete database migration tool.
✨ New Features
- PostgreSQL Support - Use PostgreSQL as your database backend for larger deployments (#1404)
- MySQL/MariaDB Support - Alternative database backend for MySQL environments (#1405)
- Database Migration Tool - Migrate data from SQLite to PostgreSQL or MySQL (#1412)
docker exec meshmonitor node /app/dist/cli/migrate-db.js \ --from "sqlite:/data/meshmonitor.db" \ --to "postgres://user:pass@host/meshmonitor"
🐛 Bug Fixes
- Fix MySQL migration schema to match app schema (prevents insert failures)
- Add automatic PostgreSQL sequence reset after migration
- Improve migration script schema handling and column mapping
- Fix PostgreSQL/MySQL sync method compatibility
- Fix auth routes async conversion for PostgreSQL support
- Handle missing settings table gracefully during service init
📖 Documentation
- Added Database Migration Guide
⚠️ Beta Notice
This is a pre-release version. SQLite remains the default and recommended database for most users. PostgreSQL/MySQL support is intended for advanced users with specific scalability or infrastructure requirements.
Full Changelog: v2.22.0...v3.0.0-beta5
Proxmox LXC Template
This release includes a Proxmox-compatible LXC container template for MeshMonitor.
Installation
- Download the
.tar.gztemplate file - Verify the SHA256 checksum (optional but recommended)
- Upload to your Proxmox server:
scp meshmonitor-*.tar.gz root@proxmox:/var/lib/vz/template/cache/ - Create a new LXC container from the template via Proxmox web UI
- Configure
/etc/meshmonitor/meshmonitor.envwith your Meshtastic node IP - Start the container and access the web UI on port 8080
Documentation
See the Proxmox LXC Deployment Guide for detailed instructions.
Limitations
- Auto-upgrade feature is not supported in LXC deployments
- Manual updates required (download new template for each version)
- Community-supported (Docker remains the primary deployment method)