Move configuration to YAML, and make the tuning knobs configurable #43
+6
-3
@@ -5,9 +5,12 @@
|
|||||||
# which refers to these by name, e.g. `token: ${NISSE_LLM_TOKEN}`. The live
|
# which refers to these by name, e.g. `token: ${NISSE_LLM_TOKEN}`. The live
|
||||||
# integration tests use the same names, from tests/integration/nisse-test.yaml.
|
# integration tests use the same names, from tests/integration/nisse-test.yaml.
|
||||||
|
|
|||||||
|
|
||||||
NISSE_LLM_TOKEN=sk-your-litellm-virtual-key
|
# llm.token: the LiteLLM virtual key (A5)
|
||||||
NISSE_MATRIX_TOKEN=syt_your_matrix_access_token
|
NISSE_LLM_TOKEN=replace-me
|
||||||
NISSE_GITEA_TOKEN=your-scoped-service-account-token
|
# matrix.token: the Matrix access token for the agent's account (A1)
|
||||||
|
NISSE_MATRIX_TOKEN=replace-me
|
||||||
|
# gitea.token: the Gitea service account's scoped token (B2)
|
||||||
|
NISSE_GITEA_TOKEN=replace-me
|
||||||
|
|
||||||
# Where the config file is, if not ./nisse-dev.yaml. Where this file is, if
|
# Where the config file is, if not ./nisse-dev.yaml. Where this file is, if
|
||||||
# not ./.env, is NISSE_ENV, which has to be set in the real environment.
|
# not ./.env, is NISSE_ENV, which has to be set in the real environment.
|
||||||
|
|||||||
Reference in new issue
Block a user
I feel like this should include some examples of the actual secrets we expect that match the example config file. Something like:
NISSE_MATRIX_TOKEN=replace-me
NISSE_GITEA_TOKEN=replace-me
NISSE_LLM_TOKEN=replace-me
They're in the file, just below this comment block. The three lines didn't change in this PR, so the diff folded them away. To make the match with the example config explicit, each one now notes which key refers to it (
llm.token,matrix.token,gitea.token), and the values arereplace-meas you suggested. Done ine1034a2c.