CI/CD

See merge request 709/mentat/pyzenkit!2

CI/CD

See merge request 709/mentat/pyzenkit!1

It is not a number anymore, we need to format it as a string.

Format it as hex to mask it due to the fact that in case of PID files
the PID in file name is not the same as PID within the file. The reason
is the fact that the PID file name is determined before daemonization.

Alternative approach would be to change the daemonization library to be
able to generate the PID file name. This however would restrict the
library too much.

Make runlog file names more unique by adding PID

There are now several default initial events scheduled by default for
each daemon. Event handlers are now defined with simple macro-like
method to reduce possibilities of errors. There is an explicit 'start'
event, that will be fired by default and that can be used by daemon
components to perform necessary startup actions, schedule additional
initial events etc.

There was a posibility of zero division, which resulted in
exception and program termination.

The py:mod role does not exist on PyPI and the linter is throwing
errors, because it would not be correctly rendered to HTML.

Current version of unit tests needs redesign to be usable. I have
disabled them to make our automated build system work.

Better condition for ending with empty queue. This should fix occasional invalid daemon termination with some events still present in queue.

I have unified the style and capabilities of the master makefile according to the one used in the Mentat system project.

It is capable of forcing given filesystem path to be relative to APP_ROOT_PATH, which may be necessary in some scenarios.

Implemented support for ingnoring missing configuration files and directories to BaseApp application.

There is a command line option for turning on the silent mode for missing configuration file and directory.

The pyzenkit.jsonconf library was enhanced with support for optional ignoration of missing configuration files/directories. This can be used to easy implementation of optional application configuration files.

Fixed many warnings reported by both tools.

You may now use the environment variable APP_ROOT_PATH to create a kind of lightweight chroot for the application. To make it work properly one must not provide absolute paths for the application path definitions. This feature can be used during development or deployment to contain all the application data within single directory, but at the same time allowing to override the configurations from configuration file or command line arguments.