Add sha256 checksum

Author: Oleksii Tsvietnov

CHANGELOG.md

@@ -1,17 +1,24 @@
-* 1.1.0
-    * FIX: fixed the bug in catching exit code of foregraound processes in "wait_any" mode
-    * FIX: now it ignors errors in the main exit hook
-    * ADD: on exiting from sub-process it tries to kill all possible child processes if any
-    * ADD: a new mode "boot" (`-B` command line option or `boot.*` files) that runs in the main namespace and results (like environment variables) are "visible" in all other sub-processes
-    * ADD: a new command line option `-F` that runs commands on the foreground (to run more than one foreground processes)
-    * ADD: a new command line option `-H` that runs commands on exiting
+* 1.1.6
+    * FIX: now it ignores errors in the main exit hook
+    * ADD: more examples
+    * ADD: sha256 chaeck sum for the release
+* 1.1.5
     * ADD: new command line options `-v` and `--version` to print the version
     * ADD: new command line options `-h` and `--help` to print a short help message
     * ADD: new command line options `-w` and `--workdir` to set the directory with config files
+* 1.1.4
+    * ADD: a new wait policy `wait_err` which waits for a first failed command
+    * ADD: a new stage "halt" (`-H` command line option or `halt.*` files) that runs on exit from the main process
+* 1.1.3
+    * ADD: a new command line option `-F` that runs commands on the foreground (to run more than one foreground processes)
+* 1.1.2
+    * ADD: on exiting from sub-process it tries to kill all possible child processes if any
+* 1.1.1
+    * FIX: fixed the bug in catching exit code of foregraound processes in "wait_any" mode
+* 1.1.0
+    * ADD: a new stage "boot" (`-B` command line option or `boot.*` files) that runs in the main namespace and results (like environment variables) are "visible" in all other sub-processes
     * ADD: more ways to present configs: 
         * ./trc.d/{boot,sync,async,halt}.*
         * ./trc.{boot,sync,async,halt}.*
     * ADD: examples
     * ADD: tests
-    * ADD: a new wait policy `wait_err` which waits for the first failed command
-    * CHANGE: supresses stderr for background processes

LICENSE

@@ -1,6 +1,6 @@
 The MIT License (MIT)
 
-Copyright (c) 2016 Oleksii Tsvietnov, me@vorakl.name
+Copyright (c) 2016, 2017 Oleksii Tsvietnov, me@vorakl.name
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

Makefile

@@ -7,6 +7,7 @@ SED_BIN ?= sed
 PWD_BIN ?= pwd
 BASENAME_BIN ?= basename
 GIT_BIN ?= git
+SHA256SUM_BIN ?= sha256sum 
 
 # -------------------------------------------------------------------------
 # Set a default target
@@ -57,6 +58,7 @@ push:
 
 publish:
 	@${CP_BIN} -f trc docs/
+	@(cd docs && ${SHA256SUM_BIN} trc > trc.sha256)
 
 cirelease: test setver settag publish
 	@${GIT_BIN} add .

README.md

@@ -32,7 +32,7 @@ All commands can be specified in the command line if they are relatively simple,
 if a more comprehensive scenario is needed. That's why it can be used as a simplest tool for managing 
 a group of process and be a lightweight replacement for solutions like [Supervisor](https://github.com/Supervisor/supervisor).
 
-For instance, in Docker images when TrivialRC is used as an Entrypoint, it doesn't reveal itself by default,
+For instance, in docker images when TrivialRC is used as an Entrypoint, it doesn't reveal itself by default,
 does not affect any configuration and behaves absolutely transparently. So, you can add it into
 any Dockerfiles which do not have an entrypoint yet and get by this the full control under processes 
 with fairly detailed logs of what's is going on inside a container. Please, take a look at [examples](https://github.com/vorakl/TrivialRC/tree/master/examples) for more information.
@@ -42,7 +42,7 @@ with fairly detailed logs of what's is going on inside a container. Please, take
 Basically, all you need to install TrivialRC is download the latest release of the script from `http://vorakl.github.io/TrivialRC/trc`
 and give it an execute permission. By default, it looks for configuration files in the same directory from which it was invoked but this behavior can be changed by setting a work directory (`-w|--workdir` parametr). So, if you are going to use configuration files and keep them in /etc/, then you would probably want to install the script to /etc/ as well and simply run it without specifying any parametrs.
 Another option in this case could be to install the script in a more appropriate path but don't forget to specify `--workdir /etc` parametr every time when you invoke this rc system. Both options are possible and depend more on a particular use case.
-For instance, in case of using in a Docker container, I personaly prefer to have all configuration in separate files in `trc.d/` sub-directory and copy it together with the script in `/etc/` . 
+For instance, in case of using in a docker container, I personaly prefer to have all configuration in separate files in `trc.d/` sub-directory and copy it together with the script in `/etc/` . 
 
 ### The installation on top of CentOS Linux base image
 
@@ -104,14 +104,14 @@ To increase the verbosity of rc system there are provided a few environment vari
 
 ## The wait policy
 
-The rc system reacts differentely when one of controlled processes finishes.
-Depending on the value of *RC_WAIT_POLICY* environment variable it make a decision when exactly it should stop itself.
+The rc system reacts differently when one of controlled processes finishes.
+Depending on the value of *RC_WAIT_POLICY* environment variable it makes a decision when exactly it should stop itself.
 The possible values are:
 
 * *wait_all* <br />
     stops after exiting all commands and doesn't matter wether they are synchronous or asynchronous
 * *wait_any*  [default] <br />
-    stops after exiting any of background commands and if no of a foreground command are working at that moment. It makes sense to use this mode if all commands are asynchronous (background)
+    stops after exiting any of background commands and if there are no foreground commands working at that moment. It makes sense to use this mode if all commands are asynchronous (background)
 * *wait_err* <br />
     stops after the first failed command. It make sense to use this mode with synchronous (foreground) commands only. For example, if you need to iterate synchronously over the list of command and to stop only if one of them has failed.
 * *wait_forever* <br />

docs/trc

@@ -5,20 +5,6 @@
 # Copyright (c) 2016, 2017 by Oleksii Tsvietnov, me@vorakl.name
 trc_version="v1.1.5"
 
-# --[ Environment variables ]--
-# RC_DEBUG (true|false) [false]
-#    Prints out all commands which are being executed
-# RC_VERBOSE (true|false) [false]
-#    Prints out service information
-# RC_VERBOSE_EXTRA (true|false) [false]
-#    Prints out additional service information
-# RC_WAIT_POLICY (wait_all|wait_any|wait_forever) [wait_any]
-#    - wait_all      quits after exiting the last command (back- or foreground)
-#    - wait_any      quits after exiting any command (including zero commands)
-#    - wait_forever  will be waiting forever after exiting all commands.
-#                    Usefull in case of daemons which are detaching and exiting
-#    - wait_err      quits after the first failed command
-
 set +e # Do not exit on errors by default
 if [[ "${RC_DEBUG}" = "true" ]]; then
     set -x # Turns on Debug mode

trc

@@ -5,20 +5,6 @@
 # Copyright (c) 2016, 2017 by Oleksii Tsvietnov, me@vorakl.name
 trc_version="v1.1.5"
 
-# --[ Environment variables ]--
-# RC_DEBUG (true|false) [false]
-#    Prints out all commands which are being executed
-# RC_VERBOSE (true|false) [false]
-#    Prints out service information
-# RC_VERBOSE_EXTRA (true|false) [false]
-#    Prints out additional service information
-# RC_WAIT_POLICY (wait_all|wait_any|wait_forever) [wait_any]
-#    - wait_all      quits after exiting the last command (back- or foreground)
-#    - wait_any      quits after exiting any command (including zero commands)
-#    - wait_forever  will be waiting forever after exiting all commands.
-#                    Usefull in case of daemons which are detaching and exiting
-#    - wait_err      quits after the first failed command
-
 set +e # Do not exit on errors by default
 if [[ "${RC_DEBUG}" = "true" ]]; then
     set -x # Turns on Debug mode