docs: fold swarm/secrets.md into the credentials reference
secrets.md and credentials-reference.md answered the same question from two pages. secrets.md's text now follows the reference's table and operating notes as a 'Where each secret lives' section, unchanged apart from where it sits. Every link and doc path that named secrets.md (docs, nix comments, crate READMEs) points at credentials-reference.md; anchors are unchanged.
This commit is contained in:
parent
0b03ed6c35
commit
d273fa8028
20 changed files with 629 additions and 627 deletions
|
|
@ -106,7 +106,7 @@ human account gets a new password once an operator forgets the old one.
|
|||
|
||||
## What secrets exist, and where each one lives
|
||||
|
||||
[`secrets.md`](secrets.md) tabulates every secret in the swarm, with its
|
||||
[`credentials-reference.md`](credentials-reference.md) tabulates every secret in the swarm, with its
|
||||
generator and its path, in one place — including authelia's own keys
|
||||
(session, JWT, storage-encryption, OIDC HMAC, OIDC issuer) and the two
|
||||
halves of each client secret. That page's two rules — a secret is always
|
||||
|
|
@ -314,7 +314,7 @@ gateway refuses its token too. See [`swarmctl/README.md`](../../swarmctl/README.
|
|||
in the store (or, as root on the Grafana host, from
|
||||
`/run/swarm-grafana-secrets/admin-password`)
|
||||
and calls the API with it. See [`services.md`](services.md#metrics-victoriametrics--grafana)
|
||||
and [`secrets.md`](secrets.md). SSO logins are the everyday way in, which
|
||||
and [`credentials-reference.md`](credentials-reference.md). SSO logins are the everyday way in, which
|
||||
is why `swarm.grafana.oidc.role` defaults to `Admin`.
|
||||
The three secrets Grafana reads live on the host's tmpfs, so after a reboot
|
||||
Grafana stays down (no login, no dashboards) until the secret store
|
||||
|
|
|
|||
Loading…
Reference in a new issue