tools/modules/initialize/init_args.sh lines 45-59: the path variables are being
built directly from PROJECT_ROOT which, when unset, produces absolute paths like
/src and /lib; ensure PROJECT_ROOT is set first (preferably defaulting to the
script directory detected via dirname "${BASH_SOURCE[0]}" or to "$PWD") and then
derive the other roots using parameter expansion that falls back to that safe
PROJECT_ROOT value; update the file to initialize SCRIPT_DIR if needed, set
PROJECT_ROOT="${PROJECT_ROOT:-$SCRIPT_DIR}" (or similar), and then keep the
existing assignments so they never expand from an empty PROJECT_ROOT.

In tools/modules/initialize/init_args.sh around lines 73 to 100, DEFAULT_ADAPTER
should default to "lo" when detection fails and several continued pipeline lines
have editorconfig/linter style issues (trailing whitespace and space-indented
continuation). Change the DEFAULT_ADAPTER fallback from empty string to "lo"
(matching set_runtime_variables), ensure subsequent uses check [[ -n
"${DEFAULT_ADAPTER:-}" ]] still work, and collapse or re-indent the multi-line
pipelines onto single lines (or use tab-indented continuations) to remove
trailing spaces and satisfy the linter; no code logic change beyond the "lo"
default and whitespace/continuation formatting fixes.

#!/bin/bash
# First, let's examine PR #665 to understand the variable naming conventions
gh pr view 665 --repo armbian/configng --json title,body,files | jq -r '.body'

#!/bin/bash
# Let's also look at the files changed in PR #665 to understand the variable structure
gh pr view 665 --repo armbian/configng --json files | jq -r '.files[].filename'

#!/bin/bash
# Let's examine the actual content of key files from PR #665 to see variable naming patterns
gh pr diff 665 --repo armbian/configng | head -100

#!/bin/bash
# Let's search for variable usage patterns in the current codebase to understand naming conventions
rg -n "^[A-Z_]+=.*" --type=sh -A 2 -B 2 | head -50

#!/bin/bash
# Let's also look at the set_runtime_variables function that was mentioned in the CodeRabbit comment
rg -n "set_runtime_variables" --type=sh -A 10 -B 5

# Current concept → Real variable names
PROJECT_NAME → CONFIG_PROJECT_NAME="armbian-configng"
PROJECT_VERSION → CONFIG_VERSION="2.0.0" 
PROJECT_ROOT → SRC_PATH (already exists in codebase)

# OS & System info (these align with existing patterns)
DISTRO → DISTRO (keep as-is)
DISTROID → DISTROID (keep as-is) 
ARCHID → ARCH (shorter, more standard)
KERNELID → KERNEL_VERSION
HOSTNAME → BOARD_NAME (aligns with Armbian convention)

# Network information
DEFAULT_ADAPTER → NET_ADAPTER
LOCALIPADD → LOCAL_IP_ADDRESS
LOCALSUBNET → LOCAL_SUBNET
DEFAULT_GATEWAY → GATEWAY_IP
HAS_INTERNET → INTERNET_STATUS
DNS_SERVERS → DNS_LIST

# Directory structure
TOOLS_ROOT → TOOLS_DIR
LIB_ROOT → LIB_DIR
DOCS_ROOT → DOCS_DIR

_show_vars() {
    # Export format for process substitution usage
    cat <<-EOF
	export CONFIG_PROJECT_NAME="$PROJECT_NAME"
	export CONFIG_VERSION="$PROJECT_VERSION"
	export DISTRO="$DISTRO"
	export DISTROID="$DISTROID"
	export ARCH="$ARCHID"
	export KERNEL_VERSION="$KERNELID"
	export BOARD_NAME="$HOSTNAME"
	export NET_ADAPTER="$DEFAULT_ADAPTER"
	export LOCAL_IP_ADDRESS="$LOCALIPADD"
	export LOCAL_SUBNET="$LOCALSUBNET"
	export GATEWAY_IP="$DEFAULT_GATEWAY"
	export INTERNET_STATUS="$HAS_INTERNET"
	export DNS_LIST="$DNS_SERVERS"
	export SRC_PATH="$PROJECT_ROOT"
	export TOOLS_DIR="$TOOLS_ROOT"
	export LIB_DIR="$LIB_ROOT"
	export DOCS_DIR="$DOCS_ROOT"
	# OS release variables (dynamic from /etc/os-release)
	$(grep -E '^[A-Z_].*=' /etc/os-release 2>/dev/null || true)
	$(grep -E '^[A-Z_].*=' /etc/armbian-release 2>/dev/null || true)
	EOF
}

# Source all variables into current shell
source <(init_vars show)

# Or with the process substitution syntax you mentioned
. <(init_vars show)

#!/bin/bash
# Let's look at the complete set_runtime_variables function to understand the actual variable names used
cat tools/modules/functions/set_runtime_variables.sh

#!/bin/bash
# Let's examine what variables are actually being used across the codebase
rg -n "^[[:space:]]*[A-Z_][A-Z0-9_]*=" --type=sh tools/modules/functions/set_runtime_variables.sh

#!/bin/bash
# Let's also look for existing variable patterns in the main config and other files
find tools/modules -name "*.sh" -exec grep -l "DIALOG\|PROJECT\|SRC\|LIB" {} \; | head -5 | xargs cat | grep -E "^[A-Z_].*=" | head -20

# Configuration system (from PR #665)
CONFIG_FILE="/etc/armbian-config"
DOMAIN="${DOMAIN:-}"                    # From PR #665 SWAG integration

# Project identification  
PROJECT_NAME="armbian-configng"         # Real project name
PROJECT_VERSION="2.0.0"                # Keep version as-is
SRC_PATH="${PROJECT_ROOT}"              # Existing pattern from codebase

# These already exist in set_runtime_variables.sh
DISTRO="${ID:-Unknown}"                 # From /etc/os-release  
DISTROID="${VERSION_CODENAME:-Unknown}" # From /etc/os-release
ARCHID="$(uname -m)"                    # Architecture
KERNELID="$(uname -r)"                  # Kernel version
HOSTNAME="$(hostname)"                  # System hostname

DEFAULT_ADAPTER="${DEFAULT_ADAPTER:-lo}" # Network interface
LOCALIPADD="${LOCALIPADD:-}"            # Local IP address
LOCALSUBNET="${LOCALSUBNET:-}"          # Local subnet
DEFAULT_GATEWAY="${DEFAULT_GATEWAY:-}"   # Gateway IP
HAS_INTERNET="${HAS_INTERNET:-no}"      # Internet connectivity
DNS_SERVERS="${DNS_SERVERS:-}"          # DNS server list

_show_vars() {
    # Source existing config if available
    [[ -f "$CONFIG_FILE" ]] && source "$CONFIG_FILE" 2>/dev/null || true
    
    # Output variables in export format for process substitution
    cat <<-'EOF'
	# Configuration system variables
	export CONFIG_FILE="/etc/armbian-config"
	export DOMAIN="${DOMAIN:-}"
	
	# Project variables
	export PROJECT_NAME="armbian-configng"
	export PROJECT_VERSION="2.0.0"
	export SRC_PATH="${PROJECT_ROOT}"
	export TOOLS_ROOT="${TOOLS_ROOT:-${PROJECT_ROOT}/tools}"
	export LIB_ROOT="${LIB_ROOT:-${PROJECT_ROOT}/lib}"
	
	# System information
	export DISTRO="${DISTRO}"
	export DISTROID="${DISTROID}" 
	export ARCHID="${ARCHID}"
	export KERNELID="${KERNELID}"
	export HOSTNAME="${HOSTNAME}"
	
	# Network information
	export DEFAULT_ADAPTER="${DEFAULT_ADAPTER}"
	export LOCALIPADD="${LOCALIPADD}"
	export LOCALSUBNET="${LOCALSUBNET}"
	export DEFAULT_GATEWAY="${DEFAULT_GATEWAY}"
	export HAS_INTERNET="${HAS_INTERNET}"
	export DNS_SERVERS="${DNS_SERVERS}"
	
	# Dialog system
	export DIALOG="${DIALOG:-whiptail}"
	export BACKTITLE="${BACKTITLE}"
	export TITLE="${TITLE}"
	EOF
    
    # Append OS release variables dynamically
    [[ -f /etc/os-release ]] && grep -E '^[A-Z_].*=' /etc/os-release 2>/dev/null | sed 's/^/export /' || true
    [[ -f /etc/armbian-release ]] && grep -E '^[A-Z_].*=' /etc/armbian-release 2>/dev/null | sed 's/^/export /' || true
}

# 1. Source all variables into current environment
source <(init_vars show)

# 2. Alternative sourcing syntax  
. <(init_vars show)

# 3. Save to file for later sourcing
init_vars show > /tmp/config_vars.sh
source /tmp/config_vars.sh

# 4. Use in other scripts
eval "$(init_vars show)"

# Read existing config values
source <(init_vars show)

# Modify and save back (using set_config_var from PR #665)
set_config_var "DOMAIN" "mynewdomain.org" "$CONFIG_FILE"

# Re-read updated values
source <(init_vars show)

#!/bin/bash
# Let's examine the current init_args.sh file structure more carefully
cat tools/modules/initialize/init_args.sh | head -50

#!/bin/bash
# Now let's look at the _show_vars function specifically
grep -A 20 "_show_vars" tools/modules/initialize/init_args.sh

#!/bin/bash
# Let's see what variables are actually defined in the current implementation
grep -n "=" tools/modules/initialize/init_args.sh | grep -v "module_options" | head -20

DISTRO=$(lsb_release -is)              # Distribution name
DISTROID=$(lsb_release -sc)            # Distribution codename  
KERNELID=$(uname -r)                   # Kernel version
DEFAULT_ADAPTER=$(ip -4 route ls...)   # Network adapter
LOCALIPADD=$(ip -4 addr show...)       # Local IP address
LOCALSUBNET=$(echo ${LOCALIPADD}...)   # Local subnet
BACKTITLE="Contribute: https://..."    # Dialog backtitle
TITLE="Armbian configuration utility"  # Dialog title
SOFTWARE_FOLDER="/armbian"             # Software installation path

CONFIG_FILE="/etc/armbian-config"      # Central config file
DOMAIN="${DOMAIN:-}"                   # Domain for SWAG/reverse proxy
NETWORK_RENDERER=NetworkManager        # Network management system

_show_vars() {
    # Source the global config file from PR #665 if available
    [[ -f "$CONFIG_FILE" ]] && source "$CONFIG_FILE" 2>/dev/null || true
    
    # Output all variables in sourceable export format
    cat <<-EOF
	# Configuration system (PR #665 integration)
	export CONFIG_FILE="/etc/armbian-config"
	export DOMAIN="${DOMAIN:-}"
	
	# Project metadata
	export PROJECT_NAME="${PROJECT_NAME}"
	export PROJECT_VERSION="${PROJECT_VERSION}"
	export PROJECT_ROOT="${PROJECT_ROOT}"
	export TOOLS_ROOT="${TOOLS_ROOT}"
	export LIB_ROOT="${LIB_ROOT}"
	export DOCS_ROOT="${DOCS_ROOT}"
	export SOFTWARE_FOLDER="${SOFTWARE_FOLDER:-/armbian}"
	
	# System information (matching set_runtime_variables.sh)
	export DISTRO="${DISTRO}"
	export DISTROID="${DISTROID}"
	export KERNELID="${KERNELID}"
	export ARCHID="${ARCHID}"
	export HOSTNAME="${HOSTNAME}"
	
	# Network information (exact variable names from set_runtime_variables.sh)
	export DEFAULT_ADAPTER="${DEFAULT_ADAPTER}"
	export LOCALIPADD="${LOCALIPADD}"
	export LOCALSUBNET="${LOCALSUBNET}"
	export DEFAULT_GATEWAY="${DEFAULT_GATEWAY}"
	export HAS_INTERNET="${HAS_INTERNET}"
	export DNS_SERVERS="${DNS_SERVERS}"
	export NETWORK_RENDERER="${NETWORK_RENDERER:-networkd}"
	
	# Dialog system variables
	export DIALOG="${DIALOG:-whiptail}"
	export BACKTITLE="${BACKTITLE}"
	export TITLE="${TITLE}"
	export DIALOG_CANCEL="1"
	export DIALOG_ESC="255"
	
	# Transmission whitelist (if calculated)
	export TRANSMISSION_WHITELIST="${TRANSMISSION_WHITELIST:-}"
	
	# ZFS variables (if available)
	export ZFS_DKMS_VERSION="${ZFS_DKMS_VERSION:-}"
	export ZFS_KERNEL_MAX="${ZFS_KERNEL_MAX:-}"
	EOF
    
    # Dynamically append OS release variables
    [[ -f /etc/os-release ]] && grep -E '^[A-Z_].*=' /etc/os-release 2>/dev/null | sed 's/^/export /' || true
    [[ -f /etc/armbian-release ]] && grep -E '^[A-Z_].*=' /etc/armbian-release 2>/dev/null | sed 's/^/export /' || true
}

_init_vars_main() {
    # ==== CONFIGURATION SYSTEM (PR #665) ====
    CONFIG_FILE="/etc/armbian-config"
    [[ -f "$CONFIG_FILE" ]] && source "$CONFIG_FILE" 2>/dev/null || true
    
    # ==== PROJECT IDENTITY ====
    PROJECT_NAME="armbian-configng"
    PROJECT_VERSION="${PROJECT_VERSION:-2.0.0}"
    [[ -f "${PROJECT_ROOT}/VERSION" ]] && PROJECT_VERSION="$(cat "${PROJECT_ROOT}/VERSION")"
    
    # ==== REUSE EXISTING set_runtime_variables LOGIC ====
    # These variables should match exactly what set_runtime_variables.sh produces
    DISTRO=$(lsb_release -is 2>/dev/null || echo "Unknown")
    DISTROID=$(lsb_release -sc 2>/dev/null || grep "VERSION=" /etc/os-release | grep -oP '(?<=\().*(?=\))')
    KERNELID=$(uname -r)
    ARCHID=$(uname -m)
    HOSTNAME=$(hostname)
    
    # Network detection (matching set_runtime_variables.sh exactly)
    DEFAULT_ADAPTER=$(ip -4 route ls 2>/dev/null | grep default | tail -1 | grep -Po '(?<=dev )(\S+)' || echo "")
    [[ -z "${DEFAULT_ADAPTER// /}" ]] && DEFAULT_ADAPTER="lo"
    LOCALIPADD=$(ip -4 addr show dev $DEFAULT_ADAPTER 2>/dev/null | awk '/inet/ {print $2}' | cut -d'/' -f1)
    LOCALSUBNET=$(echo ${LOCALIPADD} | cut -d"." -f1-3).0/24
    
    # Additional network info (your enhancements)
    DEFAULT_GATEWAY=$(ip -4 route list exact 0.0.0.0/0 2>/dev/null | awk '{print $3}' || echo "")
    HAS_INTERNET="no"
    ping -c 1 -W 2 8.8.8.8 >/dev/null 2>&1 && HAS_INTERNET="yes"
    DNS_SERVERS=$(grep -v '^#' /etc/resolv.conf 2>/dev/null | grep nameserver | awk '{print $2}' | paste -sd "," || echo "")
    
    # Dialog system (matching set_runtime_variables.sh)
    DIALOG="${DIALOG:-whiptail}"
    BACKTITLE="${BACKTITLE:-Contribute: https://github.com/armbian/configng}"
    TITLE="${TITLE:-Armbian configuration utility}"
    
    # Software folder (from set_runtime_variables.sh)
    SOFTWARE_FOLDER="${SOFTWARE_FOLDER:-/armbian}"
}

# Load all environment variables
source <(init_vars show)
echo "Running on $DISTRO $DISTROID with IP $LOCALIPADD"

# Check internet connectivity  
source <(init_vars show)
[[ "$HAS_INTERNET" == "yes" ]] && echo "Internet available"

# Use in conditional logic
source <(init_vars show)
if [[ -n "$DOMAIN" ]]; then
    echo "SWAG domain configured: $DOMAIN"
fi

#!/bin/bash
# Let's look at the complete current _show_vars function to understand its current format
grep -A 30 "_show_vars()" tools/modules/initialize/init_args.sh

echo "PROJECT_NAME=\"${PROJECT_NAME}\""
echo "DISTRO=\"${DISTRO}\""
# ... etc

module_options+=(
	["init_vars,author"]="@tearran"
	["init_vars,feature"]="init_vars"
	["init_vars,example"]="debug help mark reset total show"
	["init_vars,desc"]="Gather system info and store variables"  # Fixed typos
	["init_vars,status"]="Active"
	["init_vars,group"]="Development"
)

_init_vars_main() {
	# ==== CONFIGURATION SYSTEM (PR #665 Integration) ====
	CONFIG_FILE="/etc/armbian-config"
	[[ -f "$CONFIG_FILE" ]] && source "$CONFIG_FILE" 2>/dev/null || true

	# ==== PROJECT IDENTITY ====
	PROJECT_NAME="armbian-configng"  # Real project name
	PROJECT_VERSION="2.0.0"
	[[ -f "${PROJECT_ROOT}/VERSION" ]] && PROJECT_VERSION="$(cat "${PROJECT_ROOT}/VERSION")"
	DIALOG="${DIALOG:-whiptail}"

	# ==== OS INFORMATION (Match set_runtime_variables.sh exactly) ====
	OS_RELEASE="/etc/armbian-release"
	OS_INFO="/etc/os-release"

	# Source OS info if readable (non-fatal)
	[[ -r "$OS_INFO" ]] && source "$OS_INFO" || true
	[[ -r "$OS_RELEASE" ]] && source "$OS_RELEASE" || true

	# Read version from file if available (overrides hardcoded version)
	[[ -f "${PROJECT_ROOT}/VERSION" ]] && PROJECT_VERSION="$(cat "${PROJECT_ROOT}/VERSION")"

	# ==== PROJECT PATHS ====
	SRC_ROOT="${PROJECT_ROOT}/src"
	LIB_ROOT="${LIB_ROOT:-${PROJECT_ROOT}/lib}"
	TOOLS_ROOT="${TOOLS_ROOT:-${PROJECT_ROOT}/tools}"
	SOFTWARE_FOLDER="${SOFTWARE_FOLDER:-/armbian}"  # From set_runtime_variables.sh

	# ==== TUI VARIABLES (Match set_runtime_variables.sh) ====
	BACKTITLE="${BACKTITLE:-"Contribute: https://github.com/armbian/configng"}"
	TITLE="${TITLE:-"Armbian configuration utility"}"

	# ==== SYSTEM INFORMATION (Exact logic from set_runtime_variables.sh) ====
	DISTRO=$(lsb_release -is 2>/dev/null || echo "Unknown")
	DISTROID=$(lsb_release -sc 2>/dev/null || grep "VERSION=" /etc/os-release | grep -oP '(?<=\().*(?=\))' || echo "Unknown")
	ARCHID=$(uname -m)
	KERNELID=$(uname -r)
	HOSTNAME=$(hostname)

	# ==== NETWORK INFORMATION (Exact logic from set_runtime_variables.sh) ====
	DEFAULT_ADAPTER=$(ip -4 route ls 2>/dev/null | grep default | tail -1 | grep -Po '(?<=dev )(\S+)' || echo "")
	[[ -z "${DEFAULT_ADAPTER// /}" ]] && DEFAULT_ADAPTER="lo"
	LOCALIPADD=$(ip -4 addr show dev $DEFAULT_ADAPTER 2>/dev/null | awk '/inet/ {print $2}' | cut -d'/' -f1 || echo "")
	LOCALSUBNET=$(echo ${LOCALIPADD} | cut -d"." -f1-3).0/24

	# Additional network info (your enhancements)
	DEFAULT_GATEWAY=$(ip -4 route list exact 0.0.0.0/0 2>/dev/null | awk '{print $3}' || echo "")
	HAS_INTERNET="no"
	ping -c 1 -W 2 8.8.8.8 >/dev/null 2>&1 && HAS_INTERNET="yes"
	DNS_SERVERS=$(grep -v '^#' /etc/resolv.conf 2>/dev/null | grep nameserver | awk '{print $2}' | paste -sd "," || echo "")

	# Network renderer detection (from set_runtime_variables.sh)
	if command -v systemctl >/dev/null 2>&1; then
		if systemctl is-active NetworkManager >/dev/null 2>&1; then
			NETWORK_RENDERER="NetworkManager"
		else
			NETWORK_RENDERER="networkd"
		fi
	else
		NETWORK_RENDERER="unknown"
	fi

	# Create transmission whitelist (from set_runtime_variables.sh logic)
	TRANSMISSION_WHITELIST=$(echo ${LOCALIPADD} | cut -d"." -f1-3)".*"
}

_show_vars() {
	# Source existing config to pick up any stored values
	[[ -f "$CONFIG_FILE" ]] && source "$CONFIG_FILE" 2>/dev/null || true

	# Output in proper export format for process substitution
	cat <<-EOF
	# Armbian ConfigNG Environment Variables - Generated $(date)
	# Source this with: source <(init_vars show)
	
	# Configuration system (PR #665 integration)
	export CONFIG_FILE="$CONFIG_FILE"
	export DOMAIN="\${DOMAIN:-}"
	
	# Project metadata  
	export PROJECT_NAME="$PROJECT_NAME"
	export PROJECT_VERSION="$PROJECT_VERSION"
	export PROJECT_ROOT="$PROJECT_ROOT"
	export SRC_ROOT="$SRC_ROOT"
	export LIB_ROOT="$LIB_ROOT"
	export TOOLS_ROOT="$TOOLS_ROOT"
	export SOFTWARE_FOLDER="$SOFTWARE_FOLDER"
	
	# System information (standardized variable names)
	export DISTRO="$DISTRO"
	export DISTROID="$DISTROID"
	export ARCHID="$ARCHID"
	export KERNELID="$KERNELID"
	export HOSTNAME="$HOSTNAME"
	
	# Network information (matching set_runtime_variables.sh)
	export DEFAULT_ADAPTER="$DEFAULT_ADAPTER"
	export LOCALIPADD="$LOCALIPADD"
	export LOCALSUBNET="$LOCALSUBNET"
	export DEFAULT_GATEWAY="$DEFAULT_GATEWAY"
	export HAS_INTERNET="$HAS_INTERNET"
	export DNS_SERVERS="$DNS_SERVERS"
	export NETWORK_RENDERER="$NETWORK_RENDERER"
	export TRANSMISSION_WHITELIST="$TRANSMISSION_WHITELIST"
	
	# Dialog system variables
	export DIALOG="$DIALOG"
	export BACKTITLE="$BACKTITLE"
	export TITLE="$TITLE"
	export DIALOG_CANCEL="1"
	export DIALOG_ESC="255"
	
	# OS and Armbian release variables (dynamic)
	EOF
	
	# Append OS release variables dynamically with export prefix
	[[ -f /etc/os-release ]] && grep -E '^[A-Z_].*=' /etc/os-release 2>/dev/null | sed 's/^/export /' || true
	[[ -f /etc/armbian-release ]] && grep -E '^[A-Z_].*=' /etc/armbian-release 2>/dev/null | sed 's/^/export /' || true
}

# Load all variables into current shell environment
source <(init_vars show)

# Now you can use all the standardized variables
echo "Running $PROJECT_NAME v$PROJECT_VERSION"
echo "System: $DISTRO $DISTROID on $ARCHID"
echo "Network: $LOCALIPADD via $DEFAULT_ADAPTER"
echo "Internet: $HAS_INTERNET"

# Integration with PR #665 config system
[[ -n "$DOMAIN" ]] && echo "SWAG domain: $DOMAIN"

# Use in conditional logic
[[ "$DEFAULT_ADAPTER" != "lo" ]] && echo "Real network adapter detected"

Learnt from: Tearran
PR: armbian/configng#668
File: tools/modules/initialize/init_args.sh:0-0
Timestamp: 2025-08-29T05:48:16.966Z
Learning: The init_args.sh module in armbian/configng should use exact variable names from set_runtime_variables.sh including: DISTRO, DISTROID, KERNELID, DEFAULT_ADAPTER, LOCALIPADD, LOCALSUBNET, BACKTITLE, TITLE, SOFTWARE_FOLDER, and DIALOG. These variable names are standardized across the codebase and should not be changed to maintain compatibility.

Learnt from: Tearran
PR: armbian/configng#668
File: tools/modules/initialize/init_args.sh:167-180
Timestamp: 2025-08-29T05:39:16.651Z
Learning: Tearran is introducing an "independent drop in module concept" in the armbian/configng project where modules can function both as sourceable components and as standalone executables using BASH_SOURCE checks. The init_args.sh module is the first to implement this hybrid pattern, allowing both traditional sourcing and direct execution with built-in testing capabilities.

Learnt from: Tearran
PR: armbian/configng#530
File: tools/modules/functions/interface_checklist.sh:28-52
Timestamp: 2025-04-15T22:02:57.986Z
Learning: The Armbian configng codebase includes a set_interface() function in interface_menu.sh that validates and sets the $DIALOG variable based on available tools (whiptail, dialog, or falling back to read). This function needs to be called before interface_checklist() or other functions that depend on the $DIALOG variable.

Learnt from: Tearran
PR: armbian/configng#530
File: tools/modules/functions/interface_checklist.sh:28-52
Timestamp: 2025-04-15T22:02:57.986Z
Learning: The Armbian configng codebase already handles dialog tool validation in interface_menu.sh, which sets the $DIALOG variable based on available tools (whiptail, dialog, or falling back to read). Functions using $DIALOG in other files assume this validation has already occurred and don't need to repeat these checks.

Learnt from: Tearran
PR: armbian/configng#264
File: tools/modules/software/module_atuin.sh:2-14
Timestamp: 2025-04-13T02:25:58.772Z
Learning: In Armbian's configng modules system, the `module_options` associative array is declared in a parent library script before individual module files are sourced, so module files should not re-declare it (which is why the declaration is often commented out in module files).

Learnt from: Tearran
PR: armbian/configng#572
File: tools/modules/docs/config.docs.sh:21-24
Timestamp: 2025-04-30T23:57:15.280Z
Learning: In the armbian/configng project, `script_dir` is defined in the main script `bin/armbian-config` and is available to all sourced module files like `tools/modules/docs/config.docs.sh`. The variable doesn't need to be redefined in each module file.

Learnt from: fvalasiad
PR: armbian/configng#596
File: tools/modules/network/network_config.sh:43-43
Timestamp: 2025-05-04T21:36:25.702Z
Learning: When checking for specific adapter configurations in network scripts, be aware that simply checking one expected configuration file location may miss alternative configurations. For a more robust solution, consider checking multiple config locations or using tools like `iw` to directly determine the current mode of wireless adapters.

Learnt from: Tearran
PR: armbian/configng#529
File: tools/modules/software/module_samba.sh:1-1
Timestamp: 2025-04-12T18:00:39.337Z
Learning: In the armbian/configng project, development library files (.sh) don't require shebang directives as they're meant to be merged into production files that already have shebangs. These module files are intended to be sourced rather than executed directly.

Learnt from: Tearran
PR: armbian/configng#534
File: tools/modules/software/module_apt_browsers.sh:0-0
Timestamp: 2025-04-19T07:48:28.059Z
Learning: In the Armbian configng project, functions like `process_package_selection` are designed to accept array names as references (e.g., `array_name[@]` without quotes or expansion) rather than expanded arrays. This is implemented using indirect references with `${!variable}` syntax inside these functions.

Learnt from: Tearran
PR: armbian/configng#530
File: tools/modules/software/module_aptwizard.sh:1-248
Timestamp: 2025-04-17T17:36:45.817Z
Learning: In the armbian/configng project, module files in the tools/modules directory typically don't include shebang lines since they're meant to be sourced by other scripts rather than executed directly. The project convention is to have 98% of module files without shebangs, and this pattern should be maintained for consistency.

#!/bin/bash
# Check if export is actually used in the armbian/configng project
rg -n "export\s+" --type=sh | head -20

#!/bin/bash
# Look at existing variable display patterns in the codebase
rg -n "echo.*=.*\$" --type=sh | head -15

#!/bin/bash
# Check how other "show" functions display variables in the project
rg -n "_show|show.*\(\)" --type=sh -A 5 | head -30

_show_vars() {
    echo "# Armbian ConfigNG System Variables"
    echo "# Generated: $(date)"
    echo
    
    # Configuration system
    echo "CONFIG_FILE=\"$CONFIG_FILE\""
    [[ -n "$DOMAIN" ]] && echo "DOMAIN=\"$DOMAIN\""
    echo
    
    # Project metadata  
    echo "PROJECT_NAME=\"$PROJECT_NAME\""
    echo "PROJECT_VERSION=\"$PROJECT_VERSION\""
    echo "PROJECT_ROOT=\"$PROJECT_ROOT\""
    echo "SOFTWARE_FOLDER=\"$SOFTWARE_FOLDER\""
    echo
    
    # System information
    echo "DISTRO=\"$DISTRO\""
    echo "DISTROID=\"$DISTROID\""
    echo "ARCHID=\"$ARCHID\""
    echo "KERNELID=\"$KERNELID\""
    echo "HOSTNAME=\"$HOSTNAME\""
    echo
    
    # Network information
    echo "DEFAULT_ADAPTER=\"$DEFAULT_ADAPTER\""
    echo "LOCALIPADD=\"$LOCALIPADD\""
    echo "LOCALSUBNET=\"$LOCALSUBNET\""
    echo "DEFAULT_GATEWAY=\"$DEFAULT_GATEWAY\""
    echo "HAS_INTERNET=\"$HAS_INTERNET\""
    echo "DNS_SERVERS=\"$DNS_SERVERS\""
    echo
    
    # Dialog variables
    echo "DIALOG=\"$DIALOG\""
    echo "BACKTITLE=\"$BACKTITLE\""
    echo "TITLE=\"$TITLE\""
    echo
    
    # OS release info (if available)
    [[ -f /etc/os-release ]] && echo "# OS Release variables:" && grep -E '^[A-Z_].*=' /etc/os-release 2>/dev/null
    [[ -f /etc/armbian-release ]] && echo "# Armbian Release variables:" && grep -E '^[A-Z_].*=' /etc/armbian-release 2>/dev/null
}

# Simple variable display
./init_vars.sh show

# Or if sourced into armbian-config
init_vars show

# Save output to file for review
init_vars show > system_info.txt

Learnt from: Tearran
PR: armbian/configng#668
File: tools/modules/initialize/init_args.sh:0-0
Timestamp: 2025-08-29T05:48:16.966Z
Learning: The init_args.sh module in armbian/configng should use exact variable names from set_runtime_variables.sh including: DISTRO, DISTROID, KERNELID, DEFAULT_ADAPTER, LOCALIPADD, LOCALSUBNET, BACKTITLE, TITLE, SOFTWARE_FOLDER, and DIALOG. These variable names are standardized across the codebase and should not be changed to maintain compatibility.

Learnt from: Tearran
PR: armbian/configng#668
File: tools/modules/initialize/init_args.sh:0-0
Timestamp: 2025-08-29T05:48:16.966Z
Learning: The init_args.sh module in armbian/configng should use exact variable names from set_runtime_variables.sh including: DISTRO, DISTROID, KERNELID, DEFAULT_ADAPTER, LOCALIPADD, LOCALSUBNET, BACKTITLE, TITLE, SOFTWARE_FOLDER, and DIALOG. These variable names are standardized across the codebase and should not be changed to maintain compatibility.

Learnt from: Tearran
PR: armbian/configng#668
File: tools/modules/initialize/init_args.sh:167-180
Timestamp: 2025-08-29T05:39:16.651Z
Learning: Tearran is introducing an "independent drop in module concept" in the armbian/configng project where modules can function both as sourceable components and as standalone executables using BASH_SOURCE checks. The init_args.sh module is the first to implement this hybrid pattern, allowing both traditional sourcing and direct execution with built-in testing capabilities.

Learnt from: Tearran
PR: armbian/configng#530
File: tools/modules/functions/interface_checklist.sh:28-52
Timestamp: 2025-04-15T22:02:57.986Z
Learning: The Armbian configng codebase includes a set_interface() function in interface_menu.sh that validates and sets the $DIALOG variable based on available tools (whiptail, dialog, or falling back to read). This function needs to be called before interface_checklist() or other functions that depend on the $DIALOG variable.

Learnt from: Tearran
PR: armbian/configng#530
File: tools/modules/functions/interface_checklist.sh:28-52
Timestamp: 2025-04-15T22:02:57.986Z
Learning: The Armbian configng codebase already handles dialog tool validation in interface_menu.sh, which sets the $DIALOG variable based on available tools (whiptail, dialog, or falling back to read). Functions using $DIALOG in other files assume this validation has already occurred and don't need to repeat these checks.

Learnt from: Tearran
PR: armbian/configng#264
File: tools/modules/software/module_atuin.sh:2-14
Timestamp: 2025-04-13T02:25:58.772Z
Learning: In Armbian's configng modules system, the `module_options` associative array is declared in a parent library script before individual module files are sourced, so module files should not re-declare it (which is why the declaration is often commented out in module files).

Learnt from: Tearran
PR: armbian/configng#572
File: tools/modules/docs/config.docs.sh:21-24
Timestamp: 2025-04-30T23:57:15.280Z
Learning: In the armbian/configng project, `script_dir` is defined in the main script `bin/armbian-config` and is available to all sourced module files like `tools/modules/docs/config.docs.sh`. The variable doesn't need to be redefined in each module file.

Learnt from: Tearran
PR: armbian/configng#530
File: tools/modules/software/module_aptwizard.sh:1-248
Timestamp: 2025-04-17T17:36:45.817Z
Learning: In the armbian/configng project, module files in the tools/modules directory typically don't include shebang lines since they're meant to be sourced by other scripts rather than executed directly. The project convention is to have 98% of module files without shebangs, and this pattern should be maintained for consistency.

Learnt from: Tearran
PR: armbian/configng#668
File: tools/modules/initialize/init_args.sh:0-0
Timestamp: 2025-08-29T06:07:23.794Z
Learning: The set_runtime_variables.sh in armbian/configng establishes these key variables that must be matched exactly in independent modules: NETWORK_RENDERER (detected via systemctl/NetworkManager), DIALOG_CANCEL=1, DIALOG_ESC=255, CONFIG_FILE="/etc/armbian-config", ARMBIAN (from /etc/armbian-release), DISTRO_STATUS, SOFTWARE_FOLDER="/armbian", TRANSMISSION_WHITELIST (includes Docker subnet), ZFS_DKMS_VERSION, and ZFS_KERNEL_MAX (with fallback version logic).

Learnt from: Tearran
PR: armbian/configng#668
File: tools/modules/initialize/init_args.sh:167-180
Timestamp: 2025-08-29T05:39:16.651Z
Learning: Tearran is introducing an "independent drop in module concept" in the armbian/configng project where modules can function both as sourceable components and as standalone executables using BASH_SOURCE checks. The init_args.sh module is the first to implement this hybrid pattern, allowing both traditional sourcing and direct execution with built-in testing capabilities.

Learnt from: Tearran
PR: armbian/configng#530
File: tools/modules/functions/interface_checklist.sh:28-52
Timestamp: 2025-04-15T22:02:57.986Z
Learning: The Armbian configng codebase includes a set_interface() function in interface_menu.sh that validates and sets the $DIALOG variable based on available tools (whiptail, dialog, or falling back to read). This function needs to be called before interface_checklist() or other functions that depend on the $DIALOG variable.

Learnt from: Tearran
PR: armbian/configng#530
File: tools/modules/functions/interface_checklist.sh:28-52
Timestamp: 2025-04-15T22:02:57.986Z
Learning: The Armbian configng codebase already handles dialog tool validation in interface_menu.sh, which sets the $DIALOG variable based on available tools (whiptail, dialog, or falling back to read). Functions using $DIALOG in other files assume this validation has already occurred and don't need to repeat these checks.

Learnt from: Tearran
PR: armbian/configng#264
File: tools/modules/software/module_atuin.sh:2-14
Timestamp: 2025-04-13T02:25:58.772Z
Learning: In Armbian's configng modules system, the `module_options` associative array is declared in a parent library script before individual module files are sourced, so module files should not re-declare it (which is why the declaration is often commented out in module files).

Learnt from: Tearran
PR: armbian/configng#572
File: tools/modules/docs/config.docs.sh:21-24
Timestamp: 2025-04-30T23:57:15.280Z
Learning: In the armbian/configng project, `script_dir` is defined in the main script `bin/armbian-config` and is available to all sourced module files like `tools/modules/docs/config.docs.sh`. The variable doesn't need to be redefined in each module file.

Learnt from: Tearran
PR: armbian/configng#529
File: tools/modules/software/module_samba_lib.sh:1-1
Timestamp: 2025-04-12T20:08:12.801Z
Learning: In the armbian/configng repository, module library files (e.g., `tools/modules/software/module_samba_lib.sh`) that are intended to be sourced by other scripts don't require their own shebang directives as they inherit the shell environment from the sourcing script.

Learnt from: Tearran
PR: armbian/configng#530
File: tools/modules/software/module_aptwizard.sh:1-248
Timestamp: 2025-04-17T17:36:45.817Z
Learning: In the armbian/configng project, module files in the tools/modules directory typically don't include shebang lines since they're meant to be sourced by other scripts rather than executed directly. The project convention is to have 98% of module files without shebangs, and this pattern should be maintained for consistency.

Learnt from: dimitry-ishenko
PR: armbian/configng#496
File: tools/modules/initialize/checkpoint.sh:1-2
Timestamp: 2025-03-26T01:54:52.213Z
Learning: Module files in the armbian/configng project like `tools/modules/initialize/checkpoint.sh` don't require a shebang line as they are meant to be sourced by other scripts rather than executed directly.

Learnt from: Tearran
PR: armbian/configng#529
File: tools/modules/software/module_samba.sh:1-1
Timestamp: 2025-04-12T18:00:39.337Z
Learning: In the armbian/configng project, development library files (.sh) don't require shebang directives as they're meant to be merged into production files that already have shebangs. These module files are intended to be sourced rather than executed directly.

Learnt from: Tearran
PR: armbian/configng#534
File: tools/modules/functions/interface_checklist.sh:1-2
Timestamp: 2025-04-19T06:08:47.515Z
Learning: Files in the `tools/modules/functions/` directory are designed to be sourced by other scripts rather than executed directly, so they don't require shebang lines.