node.yaml generator

[geraveoyomama]

As a proof of concept I want to propose something like the following bash script but built into the binary.
Another behaviour could be to run nylon edit to directly open up /etc/nylon/node.cfg or something

#!/bin/bash

{
    IFS=$'\n' read -r -d '' PRIVATE_KEY;
    IFS=$'\n' read -r -d '' PUBLIC_KEY;
} < <((printf '\0%s\0' "$(./nylon key || nylon key)" 1>&2) 2>&1)
read -p "Specify node ID: " -r ID
read -p "Specify default node port: " -r -i 57175 -e PORT
read -p "nonetconfigure: " -r -i false -e NONETCONF
read -p "usesystemrouting: " -r -i true -e USESYSROUTING
read -p "Specify logpath: " -r -i  -e LOG_PATH
read -p "Specify interface name: " -r -i nylon -e INTERFACE
read -p "Should this node not route?: " -r -i false -e DISABLEROUTING
read -p "Which (comma seperated) dns servers should be used?: " -r -i 1.1.1.1:53 -e DNS
read -p "Distribution URL: " -r  DIST_URL
read -p "Distribution key: " -r  DIST_KEY

echo "key: $PRIVATE_KEY
id: $ID
port: $PORT
nonetconfigure: $NONETCONF
usesystemrouting: $USESYSROUTING
logpath: "$LOG_PATH"
interfacename: "$INTERFACE"
disablerouting: $DISABLEROUTING
dnsresolvers: [$DNS]
dist:
  url: $DIST_URL
  key: $DIST_KEY"
``` > /etc/nylon/node.yaml

[encodeous]

I think that's a great idea, especially if you are setting up many nodes.

We can have a command like nylon init --id <node> --port 123 <other args>, which creates the config, generates the private key (if not provided) and prints the public key (or other helpful info).

We can also have an interactive mode (maybe if you didn't provide the required args), which is similar to your script.

As for nylon edit, I think it might be a bit more tricky, since we would somehow launch the editor of the user's choice, which can add unnecessary complexity.

I can look into this in a few weeks, of course, contributions are welcome as well! :)