Skip to content

spupuz/VibeNVR

v1.9.9 Feature

This release adds 2 notable features for engineering teams evaluating rollout.

Published 4mo Media Servers
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

ffmpeg lightweight local-storage nvr opensource privacy
+1 more
video-surveillance

Affected surfaces

breaking_upgrade

Summary

AI summary

Added environment variables VIBENVR_FRONTEND_PORT and VIBENVR_BACKEND_PORT to configure exposed ports without editing docker‑compose files.

Full changelog

Full Changelog: https://github.com/spupuz/VibeNVR/compare/v1.9.8...v1.9.9

VibeNVR v1.9.9 — Improvements & New Features

🚀 Improvements & New Features

Configurable External Ports

  • Added two new environment variables:
    • VIBENVR_FRONTEND_PORT
    • VIBENVR_BACKEND_PORT
  • These allow you to change the exposed ports (default 8080 and 5005) without modifying docker-compose.yml.

Production Port Conflict Resolution

  • Updated the default backend port in docker-compose.prod.yml to 5005 (mapped to internal 5000).
  • Prevents the common error:
    “Bind for 0.0.0.0:5000 failed”
    when port 5000 is already in use by other services.

Updated Defaults

  • Dev Environment: Frontend 8080, Backend 5005 (via env fallback)
  • Prod Environment: Frontend 8080, Backend 5005 (via env fallback)

📦 Deployment

To use custom ports without editing compose files:

  1. Create a .env file.
  2. Add a custom port, for example:
    VIBENVR_BACKEND_PORT=5500
  3. Start the stack:
    docker compose -f docker-compose.prod.yml up -d

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track spupuz/VibeNVR

Get notified when new releases ship.

Sign up free

About spupuz/VibeNVR

All releases →

Related context

Earlier breaking changes

  • v1.28.3 Must update docker-compose.yml with TZ variable for all services

Beta — feedback welcome: [email protected]