makeworld
makeworld
Yes I believe that may be possible as well, but it's still necessary. Cause to add a node as bootstrap you need that ID anyway, and you can't connect to...
Potentially using a file such as `/etc/mesh.conf` or `/etc/mesh.conf.`. JSON will have a lot of parsers available, but it's hard for humans to write. I think [HJSON](https://hjson.org/) is a nice...
HJSON doesn't need python, look at [this](https://hjson.org/users-bin.html) easy go binary install. But because it's not easily editable maybe it's not good for a config file either.
Talking about HJSON: > Does read and write This isn't technically true. HJSON is more for human writing. If you want to do machine reading and writing, the way to...
Now I'm thinking YAML is the best way to go. Very easy to read and write for humans, and with the [yq](https://mikefarah.github.io/yq/) tool, machine read write is very easy too....
Well maybe we can write a reader/writer ourselves? YAML seems like the best format to me, but maybe it doesn't have enough tools. What are you thinking we should do?...
Nice. If both get and set work nicely, then INI style sounds okay to me.
A config file has begun taking shape in #394.
I have had the same issue with my Raspberry Pi, and @dasanchez too I believe. Maybe we should include this in out stack somehow?
I previously had this issue with the systemd daemon log, it was full of the mesh point service saying the same line, that it couldn't connect or something. Today with...