moonfire-nvr/guide/install.md
Scott Lamb c5345c1e11 simplify and fix installation instructions
* install.md, install-manual.md, and easy-install.md had a lot of
  redundancy. Rework them so the common prefix and suffix are in
  install.md and it's clear when to navigate back and forth. This
  removes from very stale references to prep.sh and cameras.sql in
  install-manual.md (which never should have mentioned these scripts
  anyway).

* remove all the SAMPLE_MEDIA_DIR, SAMPLE_FILE_DIR, and
  SAMPLE_FILE_PATH stuff from the scripts. This was too complicated
  (one variable will suffice) and inconsistent in terminology (a
  couple "samples dir" occurrences slipped through review; they
  should have been "sample file dir"). It also wasn't really useful
  enough because the procedure for a mount point is manual anyway,
  and because some installs will have multiple sample file dirs
  anyway.

* in the mount point procedure, fix the paths to be consistent. Also
  describe the "nofail" and "Requires=" config I have on my machine.

* fix some incorrect info about how to use "moonfire-nvr config" and
  describe "flush_if_sec".
2018-08-24 20:45:46 -07:00

5.3 KiB

Downloading, installing, and configuring Moonfire NVR

This document describes how to download, install, and configure Moonfire NVR on a Debian-based Linux system (such as Ubuntu or Raspbian).

(In principle, Moonfire NVR supports any POSIX-compliant system, and the main author uses macOS for development, but the documentation and scripts are intended for Linux.)

Downloading

See the github page (in case you're not reading this text there already). You can download the bleeding-edge version from the commandline via git:

$ git clone https://github.com/scottlamb/moonfire-nvr.git

Building and installing from source

There are no binary packages of Moonfire NVR available yet, so it must be built from source. To do so, you can follow either of two paths:

  • Scripted: You will run some shell scripts (after preparing one or two files, and will be completely done. This is by far the easiest option, in particular for first time builders/installers. Read more in Scripted Installation.
  • Manual: see instructions.

Moonfire NVR keeps two kinds of state:

  • a SQLite database, typically <1 GiB. It should be stored on flash if available.
  • the "sample file directories", which hold the actual samples/frames of H.264 video. These should be quite large and are typically stored on hard drives.

(See schema.md for more information.)

By now Moonfire NVR's dedicated user and database should have been created for you. Next you need to create a sample file directory.

Creating a sample file directory

...on a dedicated hard drive

If a dedicated hard drive is available, set up the mount point:

$ sudo vim /etc/fstab
$ sudo mkdir /media/nvr
$ sudo mount /media/nvr
$ sudo mkdir /media/nvr/sample
$ sudo chown moonfire-nvr:moonfire-nvr /media/nvr/sample

In the fstab you'd add a line similar to this:

/dev/disk/by-uuid/23d550bc-0e38-4825-acac-1cac8a7e091f    /media/nvr   ext4    defaults,noatime,nofail  0       2

You'll have to lookup the correct uuid for your disk. One way to do that is to issue the following commands:

$ ls -l /dev/disk/by-uuid

If you use the nofail attribute in /etc/fstab as described above, your system will boot successfully even when the hard drive is unavailable (such as when your external USB storage is unmounted). This is convenient, but you likely want to ensure the moonfire-nvr service only starts when the mounting is successful. Edit the systemd configuration to do so:

$ sudo vim /etc/systemd/system/moonfire-nvr.service $ sudo systemctl daemon-reload

You'll want to add a line like Requires=media-nvr.mount to the [Unit] section of the file.

...without a dedicated hard drive

If you don't have a dedicated hard drive available, simply create a directory owned by the dedicated user. It's convenient to place it within the installation's directory (typically /var/lib/moonfire-nvr):

$ sudo -u moonfire-nvr -H mkdir sample

Completing configuration through the UI

Once setup is complete, it is time to add sample file directory and camera configurations to the database.

You can configure the system's database through a text-based user interface:

$ sudo -u moonfire-nvr moonfire-nvr config 2>debug-log

In the user interface,

  1. add your sample file dir(s) under "Directories and retention".

  2. add cameras under "Cameras and streams".

    • There's a "Test" button to verify your settings directly from the add/edit camera dialog.

    • Be sure to assign each stream you want to capture to a sample file directory and check the "record" box.

    • flush_if_sec should typically be about 60. This causes the database to be flushed when the first instant of a completed recording second is a minute old. Lower values cause less video to be lost on power loss; higher values reduce wear on the SSD holding the SQLite database.

  3. Assign disk space to your cameras back in "Directories and retention". Leave a little slack (at least 100 MB per camera) between the total limit and the filesystem capacity, even if you store nothing else on the disk. There are several reasons this is needed:

    • The limit currently controls fully-written files only. There will be up to two minutes of video per camera of additional video.
    • The rotation happens after the limit is exceeded, not proactively.
    • Moonfire NVR currently doesn't account for the unused space in the final filesystem block at the end of each file.
    • Moonfire NVR doesn't account for the space used for directory listings.
    • If a file is open when it is deleted (such as if a HTTP client is downloading it), it stays around until the file is closed. Moonfire NVR currently doesn't account for this.

Starting it up

When finished, start the daemon and enable it for following boots:

$ sudo systemctl start moonfire-nvr
$ sudo systemctl enable moonfire-nvr

You can access the HTTP interface on http://localhost:8080/ by default.

Note that the HTTP port currently has no authentication, encryption, or logging; it should not be directly exposed to the Internet.

If the system isn't working, see the Troubleshooting guide.