This is a template module for NethServer 8 for Monica.
Instantiate the module with:
add-module ghcr.io/geniusdynamics/monica:latest 1The output of the command will return the instance name. Output example:
{"module_id": "monica1", "image_name": "monica", "image_url": "ghcr.io/geniusdynamics/monica:latest"}Let's assume that the Monica instance is named monica1.
Launch configure-module, by setting the following parameters:
host: a fully qualified domain name for the applicationhttp2https: enable or disable HTTP to HTTPS redirection (true/false)lets_encrypt: enable or disable Let's Encrypt certificate (true/false)
Example:
api-cli run configure-module --agent module/monica1 --data - <<EOF
{
"host": "monica.domain.com",
"http2https": true,
"lets_encrypt": false
}
EOFThe above command will:
- start and configure the Monica instance
- configure a virtual host for Traefik to access the instance
You can retrieve the configuration with:
api-cli run get-configuration --agent module/monica1To uninstall the instance:
remove-module --no-preserve monica1To update the instance:
api-cli run update-module --data '{"module_url":"ghcr.io/geniusdynamics/monica:latest","instances":["monica1"],"force":true}'Some configuration settings, like the smarthost setup, are not part of the configure-module action input: they are discovered by looking at some Redis keys. To ensure the module is always up-to-date with the centralized smarthost setup every time Monica starts, the command bin/discover-smarthost runs and refreshes the state/smarthost.env file with fresh values from Redis.
Furthermore, if smarthost setup is changed when Monica is already running, the event handler events/smarthost-changed/10reload_services restarts the main module service.
See also the systemd/user/monica.service file.
This setting discovery is just an example to understand how the module is expected to work: it can be rewritten or discarded completely.
Some CLI commands are needed to debug:
-
The module runs under an agent that initiates a lot of environment variables (in
/home/monica1/.config/state). It could be nice to verify them on the root terminal:runagent -m monica1 env
-
You can become runagent for testing scripts and initiate all environment variables:
runagent -m monica1
The path becomes:
echo $PATH /home/monica1/.config/bin:/usr/local/agent/pyenv/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/usr/
-
If you want to debug a container or see the environment inside:
runagent -m monica1 podman ps
Example output:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES d292c6ff28e9 localhost/podman-pause:4.6.1-1702418000 9 minutes ago Up 9 minutes 127.0.0.1:20015->80/tcp 80b8de25945f-infra d8df02bf6f4a docker.io/library/postgres:15.5-alpine3.19 --character-set-s... 9 minutes ago Up 9 minutes 127.0.0.1:20015->80/tcp postgresql-app 9e58e5bd676f docker.io/library/nginx:stable-alpine3.17 nginx -g daemon o... 9 minutes ago Up 9 minutes 127.0.0.1:20015->80/tcp monica-app -
You can see what environment variables are inside the container:
podman exec monica-app envExample output:
TERM=xterm container=podman NGINX_VERSION=1.24.0 PKG_RELEASE=1 NJS_VERSION=0.7.12 NGINX_IMAGE=docker.io/nginx:stable-alpine3.17 CONFIG_DATABASE_URI="postgresql://postgres:Nethesis,[email protected]:5432/toto" PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin HOME=/root -
You can run a shell inside the container:
podman exec -ti monica-app sh / #
Test the module using the test-module.sh script:
./test-module.sh <NODE_ADDR> ghcr.io/geniusdynamics/monica:latestThe tests are made using Robot Framework.
Translated with Weblate.
To setup the translation process:
- Add GitHub Weblate app to your repository
- Add your repository to hosted.weblate.org or ask a NethServer developer to add it to the NS8 Weblate project