[Showcase] VibeNVR – A lightweight, privacy-focused NVR (AI & Vibe Coding experiment)

  • Hi everyone,

    I wanted to share a project I’ve been working on called VibeNVR. It’s a simple, privacy-respecting local NVR designed to be fast and easy to set up without any cloud dependencies.

    Why I built this:

    As an OMV user, I’ve always valued keeping my data local and my system lean. I found that many existing NVR solutions were either too heavy for modest hardware or felt a bit dated. I decided to experiment with AI and "vibe coding" to see if I could create something modern and efficient that fits perfectly into a self-hosted environment.

    Key Features:

    • Simple & Fast: Quick setup so you can start recording in minutes.
    • Privacy-First: 100% local. No cloud, no unexpected phoning home.
    • Lightweight: Designed to run efficiently without hogging system resources.
    • Flexible: Records what you need, where you want it.

    This is still a project born out of experimentation, so I’d love to get some feedback from this community. If you’re looking for a no-fuss way to manage your cameras on your OMV setup, give it a try!

    GitHub Repository: https://github.com/spupuz/VibeNVR

    If you find it useful, a star on GitHub would be greatly appreciated! I’m looking forward to hearing your thoughts or answering any questions you might have.

    Cheers!

  • first attemp:



    I use this default (Copy&paste from github):



    code:


    and this is what show when push the check button:




  • done, still fails:


  • log:


  • Code
        # security_opt:
        #   - seccomp:unconfined 

    uncomment these line above in the following docker compose



  • log:


  • log:



    try this and provide output of command docker logs vibenvr-db



  • I've been using it for a while and haven't encountered any issues with its operation.

    I don't know if it makes a difference, but i don't use volumes; i simply bound it to a folder.

    Try copying my compose exactly as it is, modifying the "volumes" variables to always point to the same folder.



  • try this and provide output of command docker logs vibenvr-db


    I have added a delay and more retry for db setup / startup let me know

  • still error:





    log: vibeNVR.zip

  • still error:




    log: vibeNVR.zip

    Used last docker compose and properly configured the .env?

  • yes, i use this:



    and.


Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!