* The creation of Python virtual environment is now a separate makefile target.
* The 'develop' target now reuses already defined targets.
* Using python-dotenv to local configuration customizations.

(Redmine issue: #3387,#4216)

This version comes with improved application command line parameter documentation, some changes were necessary to make everything work again. (Redmine issue: #3387,#3361)

(Redmine issue: #4800)

(Redmine issue: #3387)

(Redmine issue: #3387)

Previous approach, while better in some aspects caused troubles on our automated build system, because it required for the Mentat to be correctly installed for hawat-cli to be available. (Redmine issue: #3387,#4216)

Without this it is not possible to use command line interface on our automated build system. (Redmine issue: #3387)

(Redmine issue: #4789,#4216)

(Redmine issue: #3443)

Problem with the previous solution was, that full path to the extracted strings was visible in the message .po files. So the exact path to the folder from which the developer is working was visible, which is bad for so many reasons. (Redmine issue: #4789,#4216)

Pybabel translations are now implemented as built-in Flask CLI commands and accessible from 'hawat-cli intl' utility. This approach enables users to easily customize translations for their custom Mentat system installations, or adding new languages. The drawback of this approach is, that the commands are executed within the Flask`s application context, so the application must be properly installed on target system for everything to work properly. I have kept original translation commands in the makefile for future reference.

(Redmine issue: #4789,#4216)

(Redmine issue: #3387,#4216)

(Redmine issue: #3387)

Descriptions of common parameters should be in the documentation, so that the updates do not have to be done on so many places. Additional documentation should be present only for script/daemon specific parameters. (Redmine issue: #3387)

Added missing dots instead of blank lines. (Redmine issue: #3387)

(Redmine issue: #3387)

All configuration files should by default be in a most optimal state for quick deployment without any tinkerink. The demo configuration files are redundant and increase management overhead, there is one more place that needs to be updated. (Redmine issue: #3443)

(Redmine issue: #1017,#3443)

(Redmine issue: #3443)

(Redmine issue: #3443,#3387)

(Redmine issue: #1017,#3443)

The previous value (10000) of maximum output queue size was too high and in case of system failure too many messages could be lost. On the other hand interval for checking for new messages in case the queue was previously empty was too high (30s).

It is called 'category' everywhere in the Flask, so we should call it same. (Redmine issue: #3443)

Added better project description including links to our web pages. (Redmine issue: #3387)

This commit brings in considerable amount of work. When working on this issue everything was so tied together, that I have abandoned all attempts to split it into multiple commits. There are following changes and more:

* Implementation of lightweight chroot for containing the application in single directory tree.
* Design changes in scripts and daemons to implement the lightweight chroot.
* Many configuration file changes to make everything work properly.
* Makefile additions, new targets related to running
* Updated development documentation page.

(Redmine issue: #4216)

(Redmine issue: #3387)

(Redmine issue: #3387)

(Redmine issue: #3387)

In case empty message was loaded from the message queue error was logged into the log file, but event for fetching next message from the queue was not scheduled, which basically resulted in halting of the message processing.

This was done to better decouple the library code. I have also added logging of subject and recipients for each email and added makefile target for launching development mail server. (Redmine issue: #3443)

(Redmine issue: #3443)

(Redmine issue: #3361)

This feature can be very usefull for turning off certain unwanted application or module features. For example one might want to use some kind of module implementing password authentication, but block the account registration endpoint provided by that module. (Redmine issue: #4781)

This means, that when running in production environment with logging to email enabled system administrators will be immediatelly notified about the error. (Redmine issue: #4769)

Previously some HTTP errors like Forbidden or Unauthorized returned HTML even for API endpoints. This was due to the fact, that they were executed by built-in code. I have rewritten the error handling code to be smarter and detect the appropriate response type based on client preferences. I have also consolidated and unified the error response generation. There is a new submodule hawat.errors, that contains the error response generation code and both core error handlers and AJAXMixin/HTMLMixin classes use that. I have also merged all the HTML error page templates into single one. (Redmine issue: #4769)

(Redmine issue: #3387)

Currently only built-in Flask commands run, shell, etc. are available. It can be used to launch development web server, which is now documented in development documentation page. (Redmine issue: #4216)

The logging setup is now more capable and configurable. (Redmine issue: #4216,#3443)

(Redmine issue: #3387)

There were issues with local .gitignore and commit:14be3783 does not by mistake contain the actual module code. (Redmine issue: #4220)