* add etke.cc languagetool v6.3-0 to requierements
* add languagetool to setup
* add LanguageTool to group_vars
* fix container_additional_networks var name
* add docs
* just a small clarification in the doc
* Fix incorrect closing role-specific comment
* Fix typos and improve wording on LanguageTool docs page
* Upgrade LanguageTool (v6.3-0 -> v6.3-1)
* Switch from languagetool_container_additional_networks to languagetool_container_additional_networks_auto
This is a new addition in LanguageTool v6.3-1
* Do not enable Traefik labels conditionally based on languagetool_hostname
This may have been appropriate for other roles, for which the hostname is optional, but not here.
For LanguageTool, `languagetool_hostname` is required.
* Fix languagetool section alignment
* Update languagetool.md with better explanation about n-gram data
---------
Co-authored-by: sudo-Tiz <mathis.worksome@simplelogin.fr>
Co-authored-by: Slavi Pantaleev <slavi@devture.com>
The playbook can now optimize itself based on the enabled components in
for all hosts in the inventory (`just optimize`) or for a specific host
(`just optimize-for-host HOSTNAME`).
The optimized playbook will have:
- fewer requirements (fewer roles need to be installed by `just roles`)
- a shorter and quicker to evaluate `group_vars/mash_servers` file
- a `setup.yml` file which includes less roles
Running the playbook optimized is still work in progress.
There still probably exist various role dependencies in the group-vars file, etc.
The `optimize-reset` command aims to restore your playbook to a
non-optimized state, which should work as before (and not experience bugs).
The playbook takes care to notice of changes to the various files in
`templates/` (`setup.yml`, `requirements.yml`, `group_vars_mash_servers`)
and update your optimized or non-optimized copies that are derived from
these templates. To do this, it keeps `.srchash` files in the `run/` directory.
When it notices a change in the source file's hash (by comparing to the `.srchash` file),
it will update you to the new template.
Optimization state is stored in a file in `run/` as well (`optimization-vars-files.state`).
Should the playbook notice changes in the source `template/` files, it
should update you and re-optimize using the same parameters as before (read from the state file).
