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

VibeNVR v1.9.8 — Improvements & New Features

🚀 Improvements & New Features

Restored PostgreSQL Backend

The database has been switched back from SQLite to PostgreSQL, providing:

• Better performance
• Improved concurrency handling
• Higher reliability for production environments

This resolves the consistency issues previously observed with SQLite.

Flexible Volume Configuration via .env

Support for a .env file has been added, allowing you to customize storage paths without modifying docker-compose.yml.

You can now define:

• VIBENVR_DATA (e.g., ./data)
• VIBENVR_DB_DATA (e.g., ./db_data)

Why this matters:
Your custom local paths will no longer be overwritten when pulling updates to docker-compose.yml.
If no .env file is present, the system automatically falls back to standard Docker named volumes.

Startup Stability Improvements

• Frontend: The entrypoint script now waits for both the backend and engine to become reachable before launching Nginx, eliminating “host not found” errors and startup loops.
• Backend: Startup logic has been migrated to FastAPI’s modern lifespan events, ensuring proper initialization of the database and background services (Motion/Storage).

🐛 Bug Fixes

• Docker Network Resolution: Fixed an issue where frontend and engine services could not communicate due to missing network definitions in docker-compose.yml.
• Log Management: All logs are now consolidated under /data/logs, ensuring persistence and easier debugging.
• Production Parity: docker-compose.prod.yml is now aligned with the development configuration (volumes, networks, log paths, dependencies).
• Code Fixes: Corrected indentation issues in main.py and added missing imports in motion_service.py that prevented backend startup.

📘 How to Use the New .env Configuration (Optional)

If you prefer storing data in specific local folders instead of Docker volumes, create a .env file in the project root and define your paths.