Skip to content

ERPnext Module for Nethserver 8 Free and Open Source Enterprise Resource Planning (ERP)

License

Notifications You must be signed in to change notification settings

geniusdynamics/ns8-erp-next

Repository files navigation

ns8-erpnext

Install

Instantiate the module with:

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

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

{"module_id": "erpnext1", "image_name": "erpnext", "image_url": "ghcr.io/geniusdynamics/erpnext:latest"}

Configure

Let's assume that the mattermost instance is named erpnext1.

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/erpnext1 --data - <<EOF
{
  "host": "erpnext.domain.com",
  "http2https": true,
  "lets_encrypt": false
}
EOF

The above command will:

  • start and configure the erpnext instance
  • configure a virtual host for trafik to access the instance

Get the configuration

You can retrieve the configuration with

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

Update Configuration

You can retrieve the configuration with

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

Running ERPNEXT COMMANDS

ErpNext provides a huge set of internal commands for managing and runnign erpnext found here https://frappeframework.com/docs/user/en/bench/reference and commands cheatsheet

https://frappeframework.com/docs/user/en/bench/resources/bench-commands-cheatsheet

To Run any of these Commands in NEthserver 8, you will need to ssh erpnext12@localhost WHile inside there, to run Erpnext Bench Commands

podman exec backend bench list-apps

Uninstall

To uninstall the instance:

remove-module --no-preserve erpnext1

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

See also the systemd/user/erp-next.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 are needed to debug

  • The module runs under an agent that initiate a lot of environment variables (in /home/erpnext1/.config/state), it could be nice to verify them on the root terminal

    runagent -m erpnext1 env

  • you can become runagent for testing scripts and initiate all environment variables

    runagent -m erpnext1

the path become :

    echo $PATH
    /home/erpnext1/.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 environment inside runagent -m erpnext1
podman ps
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  erpnext-app

you can see what environment variable is inside the container

podman exec  erp-next-app env
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=erpnext
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=erpnext
MARIADB_DB_PASSWORD=erpnext
MARIADB_DB_PORT=3306
HOME=/root

you can run a shell inside the container

podman exec -ti   erpnext-app sh
/ # 

Testing

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

./test-module.sh <NODE_ADDR> ghcr.io/nethserver/erpnext:latest

The tests are made using Robot Framework

UI translation

Translated with Weblate.

To setup the translation process: