New TinyWeb instances now auto-connect to reticulum.derickphan.com:4242 so users get internet mesh connectivity out of the box without any manual Reticulum configuration. Env var overrides still supported. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
33 lines
690 B
Bash
Executable file
33 lines
690 B
Bash
Executable file
#!/bin/sh
|
|
# Generate Reticulum config with optional TCP peer
|
|
# Set RNS_TCP_HOST and RNS_TCP_PORT env vars to connect to a remote instance
|
|
|
|
CONFIG_DIR="/data/.reticulum"
|
|
CONFIG_FILE="$CONFIG_DIR/config"
|
|
|
|
mkdir -p "$CONFIG_DIR"
|
|
|
|
if [ ! -f "$CONFIG_FILE" ]; then
|
|
cat > "$CONFIG_FILE" <<EOF
|
|
[reticulum]
|
|
enable_transport = False
|
|
share_instance = Yes
|
|
|
|
[logging]
|
|
loglevel = 4
|
|
|
|
[interfaces]
|
|
[[Default Interface]]
|
|
type = AutoInterface
|
|
enabled = Yes
|
|
|
|
[[TCP Transport]]
|
|
type = TCPClientInterface
|
|
enabled = yes
|
|
target_host = ${RNS_TCP_HOST:-reticulum.derickphan.com}
|
|
target_port = ${RNS_TCP_PORT:-4242}
|
|
EOF
|
|
fi
|
|
|
|
export RNS_CONFIG_DIR="$CONFIG_DIR"
|
|
exec python app.py
|