Skip to content

Releases: LeoKon3/MizuPanel

v0.0.2

01 Jun 08:47
@LeoKon3 LeoKon3
v0.0.2
316b0e8

Choose a tag to compare

View all tags
v0.0.2 Latest
Latest

Added

  • Added the first project changelog.
  • Added Docker deployment support with a root Dockerfile, default SQLite docker-compose.yml, optional MySQL docker-compose.mysql.yml, and Docker-specific server configs under docker/.
  • Added optional MySQL storage support alongside the default SQLite storage mode.
  • Added database dialect handling for SQLite/MySQL migrations and upsert SQL.
  • Added system settings for metrics retention, with runtime updates persisted in the database.
  • Added metrics history views with selectable ranges for CPU, memory, disk, network, and load data.
  • Added in-panel node record removal confirmation dialog instead of the browser-native confirm dialog.
  • Added README architecture SVG at assets/mizupanel-architecture.svg.
  • Added README screenshot gallery with Dashboard, metrics history, system settings, add-host, and Web terminal screenshots under assets/screenshots/.
  • Added Chinese default README with English switch link and a separate README.en.md.

Changed

  • Kept SQLite as the default storage backend for simple self-hosted deployments.
  • Updated server configuration to support structured storage settings for SQLite and MySQL.
  • Updated metric retention validation to use supported values: 6h, 24h, 3d, and 7d.
  • Updated Docker Compose defaults to bind the panel to 127.0.0.1 unless MIZUPANEL_BIND_ADDR=0.0.0.0 is explicitly set.
  • Reorganized README content to prioritize core features, Docker quick start, architecture, release package deployment, and Agent setup.
  • Condensed Agent install commands into collapsible README sections.
  • Reworked token documentation into a table and registration flow.

Fixed

  • Fixed Vite proxy behavior so same-origin protected API operations such as deleting node records work through the dev server.
  • Fixed Vite dev proxy WebSocket forwarding so browser terminal connections under /api work through the frontend dev server.
  • Fixed metrics API behavior for missing nodes by returning 404 instead of empty history data.
  • Fixed history range selection so ranges beyond the configured retention are disabled and rejected.
  • Fixed MySQL migration compatibility for existing schemas by using MySQL-compatible column definitions.

Security

  • Avoided exposing database passwords through browser APIs or logs.
  • Changed MySQL Docker credentials to required environment variables instead of hardcoded deployment passwords.
  • Preserved Agent's active-connection model so target hosts do not expose Agent ports.
Assets 2
Loading