An all-powerful toolset for Motion.
Sentinel is an autonomous agent for persisting, processing and automating Motion V0.1.x governance objects and tasks.
Sentinel is implemented as a Python application that binds to a local version 0.1.x motiond instance on each Motion V0.1.x Masternode.
This guide covers installing Sentinel onto an existing 0.1.x Masternode in Ubuntu 14.04 / 16.04.
Make sure Python version 2.7.x or above is installed:
python --version
Update system packages and ensure virtualenv is installed:
$ sudo apt-get update
$ sudo apt-get -y install python-virtualenv
Make sure the local Motion daemon running is at least version 0.1.0 (10000)
$ motion-cli getinfo | grep version
Clone the Sentinel repo and install Python dependencies.
$ git clone https://github.com/motioncrypto/sentinel.git && cd sentinel
$ virtualenv ./venv
$ ./venv/bin/pip install -r requirements.txt
Set up a crontab entry to call Sentinel every minute:
$ crontab -e
In the crontab editor, add the lines below, replacing '/home/YOURUSERNAME/sentinel' to the path where you cloned sentinel to:
* * * * * cd /home/YOURUSERNAME/sentinel && ./venv/bin/python bin/sentinel.py >/dev/null 2>&1
Test the config by runnings all tests from the sentinel folder you cloned into
$ ./venv/bin/py.test ./test
With all tests passing and crontab setup, Sentinel will stay in sync with motiond and the installation is complete
An alternative (non-default) path to the motion.conf file can be specified in sentinel.conf:
motion_conf=/path/to/motion.conf
To view debug output, set the SENTINEL_DEBUG environment variable to anything non-zero, then run the script manually:
$ SENTINEL_DEBUG=1 ./venv/bin/python bin/sentinel.py
Released under the MIT license, under the same terms as MotionCore itself. See LICENSE for more info.