Don't understand the access.json
What's going on with the 'access.json'? There's a couple of username/password key value pairs, right? And then peers? What's up with the peers?
Thanks for the question, and congrats on asking the first question on our new support forum!
Yes, the simple key:value pairs are username:password combinations which will allow access to the Lynxari platform. There is no limit to how many can be present, which allows for any number of peers or API auth without giving the same access twice.
The 'peers' object lists remote Lynxari servers to which this one may initiate a peer connection. Each entry here is an object which lists the username and password for that peer. There can any number of peers listed, but no one should be repeated.
I hope that make sense. The simple key:value pairs are for outsiders connecting to this installation, while the peers are for outgoing links.
Okay I get it. Would each peer access have made more sense to show up in the peerlist.json?
All usernames and passwords are contained in one access file. The reason is so that the permissions to that file can be controlled by the OS. If the peerlist.json file contained sensitive info, then it would have to be restricted, which would make things more difficult.