spupuz/VibeNVR

v1.19.1 Breaking

This release includes 1 breaking change for platform teams planning a safe upgrade.

Published 3mo Media Servers

View tool

✓ 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

Breaking change: update docker‑compose.prod.yml to adopt new entrypoint.sh for signal handling.

Full changelog

Full Changelog: https://github.com/spupuz/VibeNVR/compare/v1.19.0...v1.19.1

📹 VibeNVR Release Notes – v1.19.1

[!WARNING]
BREAKING CHANGES: This release introduces architectural changes to process management (entrypoint.sh). You MUST update your docker-compose.prod.yml file to ensure proper signal handling and system stability.

🚀 What's New & Improved

🛡️ Resilience & Signal Handling

Atomic Update Stability: Implemented dedicated entrypoint.sh scripts for Backend and Engine. These ensure SIGTERM propagation, allowing clean shutdowns during updates.
Database Outage Grace: Global OperationalError handler returns a standard 503 Service Unavailable with component status (database: lost) instead of crashing.
Async Health Checks: The health check API is now non-blocking for long-running engine syncs.

🔍 Transparency & UX

Initialization Dashboard: Real-time status for VibeAPI, Database, and Engine. Clearly distinguishes between "Offline", "Error", and "Ready" states.
Manual Retry: "Retry Now" button added to the startup screen for faster recovery during restarts.
Storage Protection: Automatic truncation of backend.log and engine.log to 10MB on container startup.

🔄 Update Procedure (REQUIRED)

Follow these exact steps to ensure a smooth transition:

# 1. Back up your .env file
cp .env .env.bak

# 2. Retrieve the new production compose file (Breaking Change)
# Ensure you are in the project root
curl -O https://raw.githubusercontent.com/spupuz/VibeNVR/main/docker-compose.prod.yml

# 3. Pull the new 1.19.1 images
docker compose -f docker-compose.prod.yml pull

# 4. Stop the current stack
docker compose -f docker-compose.prod.yml down

# 5. Start the new stack
docker compose -f docker-compose.prod.yml up -d