decentraleyes-sysop v0.0.6
decentraleyes-sysop
Decentraleyes.net SysOp service reference implementation
Architecture
Every service in Decentraleyes.net is shipped as a standalone module to allow SysOps the freedom to:
- Determine whether or not they use each module;
- Determine when/if they upgrade them; and
- Change or even entirely rewrite them from scratch.
Each service module implements an interface made of public methods and routes. If the public interface is maintained, Decentraleyes.net doesn't care what amount of actual work is performed within the service as long as it succeeds and generates a result expected by the user per the documented interface contract of the service.
For example, a SysOp might not want to use MongoDB or might even want to use a database they created. Such a user could create a new service and write the logic needed to use their custom database while providing service as expected through Decentraleyes.net including beacons, notifications and so on.
service-options.json
The service-options.json file lets the SysOp set certain options that simply don't make sense to store in the database and/or edit (or even expose) through the web front end. Any standard text editor can be used to change the contents of service-options.json. It is simply a JavaScript Object Notation (JSON) file.
password
Must be set to a properly-hashed representation of the SysOp password. To change it from the default, either use the command line tool decentraleyes-mkpasswd or log into your node using the default password, go to the admin dashboard and change it. If changed through the admin dashboard, service-options.json will be rewritten with the change.