Hell

Command line utility to controll daemons

Usage

 $ hell [-h|-?|--help]
 $ hell [ [ add | update ] [ -d=<dir> ] [ -c=<cmd> ] [ -e=<env_file> ] | delete | show ] [ <service_name> ]
 $ hell [ start | stop | restart | reload | status ] <service_name>
 $ hell status

 Flags:
   -h, -?, --help
       See help message

   -v
       print version

 Commands:
   add
        add new service to config
        must be also passed --cmd, --dir and --env
   update
        update service in config
        must be also passed --cmd, --dir or --env
   show
        show service's config
   delete
        delete service from config

   start, stop, restart
        Start/Stop/Restart service
   reload
        Reload configuration
   status
        Print current status

 Args for commands "add", "update", "delete":
   -c=<cmd> |--cmd=<cmd>
       command how to start service
   -d=<dir> |--dir=<dir>
       dir to be changed before starting
   -e=<env_file> |--env=<env_file>
       file with enviroment variables

Dependences:

jshon - command line json parser

Configuration files

All configs are json objects

Services

Services store data about each service
key - service name
value - object with three key:

cmd - command to start your service (required)
dir - path where to run command to start your service (required)
env - file name with full path (or path from "dir") to env-file. env-file - bash file that exports enviroment variables. (optional)

Example:

{  
	"MyService": {  
		"cmd": "python3 main.py",  
		"dir": "/path/to/project/dir/",  
		"env": "/path/to/env/file"  
	}  
}

Pids

Internal config that keeps process ids
Example:

{
	"MyService": 1234
}

Example

Here are examples of usage of hell:

Create service configuration

$ hell MyService add -c=./start.sh -d=~/my/project
add service 'MyService'
arg -e was not passed.
That's not a problem, u can update info later.

Update service configuration

$ hell MyService update --env=env/file.sh
update service 'MyService'

Show service configuration

$ hell MyService show
Service config
service: 'MyService'
data: { "dir" : "/home/", "env" : "/home/riniyar/bin/unixtime", "cmd" : "./start.sh" }
Service is not running

Start service

$ hell MyService start
starting 'MyService'
service started; Pid = 11248

Show status of service

$ hell MyService status
status of 'MyService'
Service is running

Stop service

$ hell MyService stop
stopping 'MyService'
Service was stopped

Delete service configuration

$ hell MyService delete
delete service 'MyService'

Print status of all services

$ hell status  
MyService1 - Running
MyService2 - Stopped
MyService3 - Not started

moff4 / Hell