-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unify configuration formats #252
Comments
https://learnxinyminutes.com/docs/toml/ We could also do arrays:
and
|
as we never should have two routers or users with the same name i see no reason to use arrays. i think its better to user the username/routername as a key identifier on this |
i also se the use for creating eg. read-only users.. with no permissions to change/update things.. so a format witch allows multiple options pr. user is a good thing :) |
the format used for configuration files are by now quite different.
<key>:<value>
with a new element/object on everyname
key<username> <password>
What about unifying all these formats to use the same toml structure?
example polldevs format:
example secrets:
or
this later then supports multiple attributes pr. user if this is needed.
The text was updated successfully, but these errors were encountered: