Configuration¶
Every setting is a field of wiki_api.config.Settings and a WIKI_API_ prefixed
environment variable (Example: http_port is WIKI_API_HTTP_PORT).
Read from four places, first Settings arguments, then local environment .env
finally config file deploy.json.
deploy.json sits beside the keys, or wherever WIKI_API_CONFIG_FILE names. Copy
deploy.example.json for a complete one. Each install puts both somewhere already:
installed as |
|
|
|---|---|---|
PyPI |
|
|
a container |
|
|
a system package |
|
|
a checkout |
|
|
Data¶
setting |
default |
what it does |
|---|---|---|
|
|
Where the artifact and staged sources live. |
|
|
The file a surface opens. |
|
|
The staged sources, under |
|
|
Which published dataset |
|
|
Which build of it. A commit pins an older one. |
|
|
The game repositories, build time only. |
|
|
Hand corrections, build time only. |
|
|
Allocated ids, build time only. |
Surfaces¶
setting |
default |
what it does |
|---|---|---|
|
|
One of |
|
|
Set to |
|
|
|
|
|
|
|
|
Read only when the transport is |
|
|
Read only when the transport is |
|
none |
Origins the browser contract answers. |
The tools over stdio install no guard, and are the only case that starts without a key. See Keys and access.
Answer sizes¶
setting |
default |
what it does |
|---|---|---|
|
|
Rows in one relationship block of an HTTP page. |
|
|
Rows in one MCP answer. |
|
|
Near names offered for a name that matched nothing. |
|
|
How close to the best match a candidate must be. |
|
|
How close a candidate must be at all. |
|
|
|
|
|
|
The guard¶
setting |
default |
what it does |
|---|---|---|
|
|
|
|
none |
The issuer public key inline. |
|
beside the keys |
Where to read the issuer public key from. |
|
beside the keys |
The withdrawn key ids. |
|
beside the keys |
Where shut-out addresses are written. |
|
|
One caller’s steady share. |
|
|
How far a caller may run ahead of it. |
|
|
Refusals in the window before a shut-out. |
|
|
The window, in seconds. |
|
|
The first ban. Repeats grow it. |
|
|
How many callers are tracked at once. |
|
none |
Whose forwarded-for header is believed. |
See Keys and access for what these mean in practice, and Architecture for why a process serving both runs a single worker.