docs: describe the forge's OIDC secret as fetched from bao, not copied or hand-placed
sso.md still described a host-side copy unit and an operator-placed file for a forge elsewhere; secrets.md's client-secret row still named sso.clientSecretFile as the operator's route. The clientSecretFile example now shows the path swarm-bao-forge-oidc writes. Refs #5015
This commit is contained in:
parent
f6ca5f1433
commit
5658361096
3 changed files with 52 additions and 43 deletions
|
|
@ -245,7 +245,7 @@ in
|
|||
sso.clientSecretFile = lib.mkOption {
|
||||
type = lib.types.nullOr lib.types.str;
|
||||
default = null;
|
||||
example = "/var/lib/hyperhive/forge-oidc-secret";
|
||||
example = "/var/lib/forgejo-oidc/forgejo.secret";
|
||||
description = ''
|
||||
Path **inside the forge container** holding the client
|
||||
secret's plaintext.
|
||||
|
|
|
|||
Loading…
Reference in a new issue