-
Notifications
You must be signed in to change notification settings - Fork 51
Config overhaul: make some fields mandatory #938
Copy link
Copy link
Closed
Labels
Enhancement / Feature RequestSomething NewSomething NewNeeds FeedbackWhat dose the Community Think?What dose the Community Think?
Milestone
Description
Parent issue: #401
Relates to: #401 (comment)
Depends on: #936
In the current version, all config values have a default value. You can run the app without providing any config value at all.
@da2ce7 suggested forcing the system admin (who is responsible to setup the app) to provide at least some critical options like:
version = "2"
[logging]
threshold = "info"
[core]
private = false
listed = falseThey are already mandatory, but we have defined server default values, meaning you can omit the file in the TOML or JSON file, and it will use the default value. We have to remove the default values to force the users to provide the values.
Hi @da2ce7, is that list OK? (I'm already using new names even if, in some cases, those changes might not been applied yet)
UPDATE (2024-08-02)
Metadata section has changed.
[metadata]
app = "torrust-tracker"
purpose = "configuration"
schema_version = "2.0.0"
[logging]
threshold = "info"
[core]
private = false
listed = falseReactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Enhancement / Feature RequestSomething NewSomething NewNeeds FeedbackWhat dose the Community Think?What dose the Community Think?
Type
Projects
Status
Done