Jump to:
- Fetch Settings
- Set Settings is TODO
Fetch Settings
Status: Implemented 20230120
Required permissions: "o"
Request: /json/settings/get[?version=X]
Response payload example:
{
"access-log":{
"versionable":false,
"sensitive":false,
"defaultValue":"off",
"valueSource":null,
"value":null
},
...
"binary-glob":{
"versionable":true,
"sensitive":false,
"defaultValue":null,
"valueSource":"versioned",
"value":"*.gif\n*.ico\n*.jpg\n*.odp\n*.dia\n*.pdf\n*.png\n*.wav..."
},
...
"web-browser":{
"versionable":false,
"sensitive":true,
"defaultValue":null,
"valueSource":"repo",
"value":"firefox"
}
}
Each key in the payload is the name of a fossil-recognized setting, modeled as an object. The keys of that are:
defaultValue
: the setting's default value, ornull
if no default is defined.value
: The current value of that setting.valueSource
: one of ("repo"
,"checkout"
,"versioned"
, ornull
), specifying the data source where the setting was found. The settings sources are checked in this order and the first one found is the result:- If
version=X
is provided, check-inX
is searched for a versionable-settings file. If found, its value is used andvalueSource
will be"versioned"
. IfX
is not a checkin, an error response is produced with codeFOSSIL-3006
. - If a versionable setting is found in the current checkout, its
value is used and
valueSource
will be"versioned"
- If the setting is found in checkout database's
vvar
table, its value is used andvalueSource
will be"checkout"
. - If the setting is found in repository's
config
table, its value is used andvalueSource
will be"repo"
. - If no value is found,
null
is used for both thevalue
andvalueSource
results. Note that global settings are never checked because they can leak information which have nothing specifically to do with the given repository.
- If
sensitive
: a value which fossil has flagged as sensitive can only be fetched by a Setup user. For other users, they will always have avalue
andvalueSource
ofnull
.versionable
:true
if the setting is tagged as versionable, elsefalse
.
Note that settings are internally stored as strings, even if they're semantically treated as numbers. The way settings are stored and handled does not give us enough information to recognize their exact data type here so they are passed on as-is.