Config overhaul: make some fields mandatory

[josecelano]

Parent issue: #591

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 for setting up the app) to provide at least some critical options like:

version = "2"

[logging]
threshold = "info"

They 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?

UPDATE (2024-08-02)

The metadata section was updated. Only the schema_version is mandatory.

[metadata]
app = "torrust-index"
purpose = "configuration"
schema_version = "2.0.0"

[josecelano]

Hi @da2ce7 should secrets also be mandatory? For example:

• tracker.token
• auth.user_claim_token_pepper
• mail.smpt.credentials.password

They have default values and are optional.

[da2ce7]

@josecelano I guess so. I don't like the idea of the tracker running by default by insecure default values...