ryanlucchese / sentinel

EnergiCore Sentinel Engine

Energi Sentinel

An all-powerful toolset for Energi.

Sentinel is an autonomous agent for persisting, processing and automating Energi V12.1 governance objects and tasks, and for expanded functions in the upcoming Energi V13 release (Evolution).

Sentinel is implemented as a Python application that binds to a local version 12.1 energid instance on each Energi V12.1 Masternode.

This guide covers installing Sentinel onto an existing 12.1 Masternode in Ubuntu 14.04 / 16.04.

Installation

1. Install Prerequisites

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 Energi daemon running is at least version 12.1 (120100)

$ energi-cli getinfo | grep version

2. Install Sentinel

Clone the Sentinel repo and install Python dependencies.

$ git clone https://github.com/energicryptocurrency/sentinel.git && cd sentinel
$ virtualenv ./venv
$ ./venv/bin/pip install -r requirements.txt

3. Set up Cron

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

4. Test the Configuration

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 energid and the installation is complete

Configuration

An alternative (non-default) path to the energi.conf file can be specified in sentinel.conf:

energi_conf=/path/to/energi.conf

Troubleshooting

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

Contributing

Please follow the EnergiCore guidelines for contributing.

Specifically:

• Contributor Workflow

  To contribute a patch, the workflow is as follows:

  • Fork repository
  • Create topic branch
  • Commit patches

  In general commits should be atomic and diffs should be easy to read. For this reason do not mix any formatting fixes or code moves with actual code changes.

  Commit messages should be verbose by default, consisting of a short subject line (50 chars max), a blank line and detailed explanatory text as separate paragraph(s); unless the title alone is self-explanatory (like "Corrected typo in main.cpp") then a single title line is sufficient. Commit messages should be helpful to people reading your code in the future, so explain the reasoning for your decisions. Further explanation here.

License

Released under the MIT license, under the same terms as EnergiCore itself. See LICENSE for more info.