Ah yes, "up" not valid command AND message unreadable

[Merith-TK]

╭────────────────────────────────────────────────────────────────────────────────╮
│💥 AN ERROR OCCURRED WHILE HANDLING YOUR COMMAND                                │
│   unknown command "up" for "mittnitectl"                                       │
│                                                                                │
│   If you think this is a bug, please feel free to open an issue at             │
│   https://github.com/mittwald/mittnite                                         │
╰────────────────────────────────────────────────────────────────────────────────╯

[martin-helmich]

1. The server process is mittnite, not mittnitectl, so you're probably going to want to invoke that, instead of mittnitectl
2. Error messages are supposed to be rendered in red, using ANSI escape codes. Which terminal emulator are you using?

[Merith-TK]

Windows Terminal, sshed into OpenWRT based Router

And I am afraid I will need compile instructions for this then as the target machine is linux/mipsle

[Merith-TK]

Figured out the build steps and got it setup on my router, useful little thing, need to look into the service configs more, here is the init.d script I used to make it just work

#!/bin/sh

MITTNITE_BIN="/mnt/.sbin/mittnite"
CONFIG_DIR="/mnt/.init/"
LOG_FILE="/var/log/mittnite.log"

case "$1" in
  start)
    echo "Starting mittnite..."
    $MITTNITE_BIN up --api --config-dir $CONFIG_DIR >> $LOG_FILE 2>&1 &
    ;;
  stop)
    echo "Stopping mittnite..."
    killall mittnite
    ;;
  restart)
    echo "Restarting mittnite..."
    $0 stop
    sleep 1
    $0 start
    ;;
  *)
    echo "Usage: $0 {start|stop|restart}"
    exit 1
    ;;
esac

exit 0

[Merith-TK]

if you could add this script to an option?

maybe a feature for mittnite process is an inject-init command, where it will inject itself into the init system (if supported) and use an designated config folder? (default to /etc/mittnite.d)

making this an feature request