• 0.1.1 18d6289807

    NexaPG 0.1.1
    All checks were successful
    PostgreSQL Compatibility Matrix / PG14 smoke (push) Successful in 8s
    PostgreSQL Compatibility Matrix / PG15 smoke (push) Successful in 8s
    PostgreSQL Compatibility Matrix / PG16 smoke (push) Successful in 8s
    PostgreSQL Compatibility Matrix / PG17 smoke (push) Successful in 8s
    PostgreSQL Compatibility Matrix / PG18 smoke (push) Successful in 8s
    Stable

    nessi released this 2026-02-13 08:10:35 +00:00 | 41 commits to main since this release

    Added

    • New Service Information section in the sidebar and UI.

    • New backend endpoints for service/runtime metadata:

      • GET /api/v1/service/info
      • POST /api/v1/service/info/check
    • Persistent service info storage (service_info_settings) for:

      • latest checked version
      • update status
      • last check timestamp / error state
    • Initial Alembic migration for service info:

      • 0008_service_settings.py

    Changed

    • Update checks now use the official upstream NexaPG repository:
      • git.nesterovic.cc/nessi/NexaPG
    • Version check logic is now release-focused (latest published release), easier to manage than commit-based checks.
    • Service Information page is now read-only for end users.

    Security / Hardening

    • Removed .env-based version override.
    • APP_VERSION is no longer user-configurable via environment.
    • NexaPG version is now controlled only in code (config.py NEXAPG_VERSION).

    Docs

    • Updated README for Service Information and update-check behavior.
    • Updated .env.example to remove APP_VERSION and related mutable version settings.

    Upgrade Notes

    • Run migrations when upgrading from 0.1.0:
      • make migrate
    • Restart backend after update:
      • make down && make up
    • If you previously used APP_VERSION in .env, it is now ignored/removed by design.
    Downloads
  • 0.1.0 0445a72764

    NexaPG v0.1.0 — Initial Public Release
    All checks were successful
    PostgreSQL Compatibility Matrix / PG14 smoke (push) Successful in 8s
    PostgreSQL Compatibility Matrix / PG15 smoke (push) Successful in 8s
    PostgreSQL Compatibility Matrix / PG16 smoke (push) Successful in 8s
    PostgreSQL Compatibility Matrix / PG17 smoke (push) Successful in 8s
    PostgreSQL Compatibility Matrix / PG18 smoke (push) Successful in 8s
    Stable

    nessi released this 2026-02-13 08:00:59 +00:00 | 43 commits to main since this release

    NexaPG 0.1.0 is the first public release of our PostgreSQL monitoring platform focused on practical operations, clear visibility, and modern UX.

    Highlights

    • Multi-target PostgreSQL monitoring (remote instances)

    • FastAPI backend + React frontend + PostgreSQL core DB

    • Docker Compose stack for quick deployment

    • RBAC with JWT authentication (admin, operator, viewer)

    • Target credential encryption at rest

    • Structured audit logging and backend JSON logs

    • Background polling collector with configurable interval

    • Core PostgreSQL metrics and system views:

      • pg_stat_database
      • pg_stat_activity
      • pg_stat_bgwriter / pg_stat_checkpointer compatibility handling
      • pg_locks
      • optional pg_stat_statements
    • DBA-ready Target Detail with database overview, replication/storage insights, and charts

    • Easy/DBA view mode toggle for different user skill levels

    • Query Insights with ranking, search, optimization hints, and pagination

    • Alerting system with warning/alert severities

      • built-in standard alerts
      • custom SQL alerts
      • realtime alert updates + in-app toast notifications
    • Target owner model:

      • assign responsible users per target
      • alert emails sent only to assigned owners
    • SMTP admin settings with test mail and customizable templates

    • Service Information page with release-based upstream update check

    • PostgreSQL compatibility smoke tests for versions 14 to 18

    • Notes

    • This is the baseline release and foundation for upcoming features.

    • Query Insights require pg_stat_statements on monitored targets where enabled.

    • Update detection is based on published upstream releases.

    Downloads