Skip to content

History

This page summarizes the visible project history of UnyPort from the repository and release files available in docker_unyport.

May 3, 2026 - initial dashboard and network foundation

The first commits on 2026-05-03 established the early product baseline:

  • Initial dashboard work
  • Upgraded presentation
  • First network chart and data additions

These commits mark the shift from idea to working monitoring surface.

May 4, 2026 - SSE refactoring

On 2026-05-04, the project history shows an SSE refactor. This matters because the current product experience still depends heavily on live snapshot delivery rather than periodic manual refreshes.

May 9, 2026 - repository framing and README

Commits on 2026-05-09 added:

  • Repository mirroring context
  • Public README work
  • Image-hosting corrections

This is the point where UnyPort becomes easier to present as a public project rather than only a local experiment.

May 30, 2026 - packaging refactor

The 2026-05-30 refactor is one of the most meaningful packaging steps in the visible history:

  • UPX compression for a smaller package
  • Broader runtime cleanup
  • Stronger compact-binary positioning

This aligns with the single-binary promise repeated in the README.

June 6, 2026 - UI and restart-history expansion

Several commits on 2026-06-06 added:

  • A hamburger menu
  • A git-style reboot map
  • A network-map refactor

These changes clearly move UnyPort toward a more complete operator UI rather than a raw metrics panel.

June 7, 2026 - public release v0.1.0

On 2026-06-07, the repository history shows:

  • Release preparation
  • Release-note polish
  • Tag v0.1.0
  • App versioning work

The bundled CHANGELOG.md and RELEASE-v0.1.0.md both confirm that v0.1.0 is the first public release.

June 18 to July 10, 2026 - documentation refinement

Later commits focused on documentation updates:

  • 2026-06-18: Demo URL and Docker bind documentation fixes
  • 2026-07-10: History update

By July 10, 2026, the visible repository story is therefore a monitoring-first control portal that already has a public release, compact packaging work and a clearer documentation posture.