Refactor server configuration parsing #61
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Project/Client
Project/Server
Project/liblanbassador
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
luca0N/lanbassador#61
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I think it would be nicer to have some kind of configuration parser (in a new source file) that offers 3 different ways of setting options: environment keys, command line options, and in the configuration file, in this order of precedence. This way, it will be a lot easier of implementing new customizable options in the server without having to check where the value is set (if at all).
I had this idea while implementing a new option in the configuration file for specifying the interface name. Instead of creating a separate issue for this, this issue will be used to track that.