Skip to content

Repository files navigation

ns8-termix

Build Status

NethServer 8 module for the Termix application, providing a web-based terminal interface.

Table of Contents

Install

Instantiate the module with:

add-module ghcr.io/geniusdynamics/termix:latest 1

The output of the command will return the instance name. Output example:

{
  "module_id": "termix1",
  "image_name": "termix",
  "image_url": "ghcr.io/geniusdynamics/termix:latest"
}

Configure

Let's assume that the termix instance is named termix1.

Launch configure-module, by setting the following parameters:

  • host: a fully qualified domain name for the application
  • http2https: 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/termix1 --data - <<EOF
{
  "host": "termix.domain.com",
  "http2https": true,
  "lets_encrypt": false
}
EOF

The above command will:

  • start and configure the termix instance
  • configure a virtual host for traefik to access the instance

Update

To update the module to a new version:

api-cli run update-module --data '{
  "module_url": "ghcr.io/geniusdynamics/termix:latest",
  "instances": ["termix1"],
  "force": true
}'

Get the Configuration

You can retrieve the configuration with:

api-cli run get-configuration --agent module/termix1

Uninstall

To uninstall the instance:

remove-module --no-preserve termix1

Smarthost setting discovery

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 termix 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 termix is already running, the event handler events/smarthost-changed/10reload_services restarts the main module service.

See also the systemd/user/termix.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.

Debug

Some CLI commands are needed to debug the module.

  • The module runs under an agent that initiates many environment variables (in /home/termix1/.config/state). It could be useful to verify them on the root terminal:

    runagent -m termix1 env
  • You can become the runagent for testing scripts and initiate all environment variables:

    runagent -m termix1

    The PATH becomes:

    /home/termix1/.config/bin:/usr/local/agent/pyenv/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/usr/
    
  • To debug a container or see the environment inside, first run:

    runagent -m termix1

    Then list containers:

    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/mariadb:10.11.5          --character-set-s...  9 minutes ago  Up 9 minutes  127.0.0.1:20015->80/tcp  mariadb-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  termix-app
    
  • To see environment variables inside the container:

    podman exec termix-app env

    Example output:

    PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
    TERM=xterm
    PKG_RELEASE=1
    MARIADB_DB_HOST=127.0.0.1
    MARIADB_DB_NAME=termix
    MARIADB_IMAGE=docker.io/mariadb:10.11.5
    MARIADB_DB_TYPE=mysql
    container=podman
    NGINX_VERSION=1.24.0
    NJS_VERSION=0.7.12
    MARIADB_DB_USER=termix
    MARIADB_DB_PASSWORD=termix
    MARIADB_DB_PORT=3306
    HOME=/root
    
  • To run a shell inside the container:

    podman exec -ti termix-app sh

Testing

Test the module using the test-module.sh script:

./test-module.sh <NODE_ADDR> ghcr.io/geniusdynamics/termix:latest

The tests are made using Robot Framework.

UI Translation

Translated with Weblate.

To set up the translation process:

Releases

Packages

Contributors

Languages