treefmt: apply prettier
Pure `nix fmt` output from the commit before this one — no hand edits. 203 files: 52 md, 42 tsx, 32 js, 32 css, 21 ts, 13 html, 8 json, 3 mjs. Reproduce with `nix develop -c nix fmt` on the parent commit; the result should be byte-identical to this tree. None of the 13 `.prettierignore` entries appears here — verified by intersecting the changed-file list against the ignore file, with a control proving the intersection finds a match when one exists.
This commit is contained in:
parent
5d24bedd60
commit
39b95c2ede
203 changed files with 10090 additions and 6085 deletions
|
|
@ -40,7 +40,7 @@ directly. That is the whole arrangement — neither keeps a private copy it
|
|||
considers canonical.
|
||||
|
||||
It used to be otherwise, and the seam was real: each side had its own
|
||||
`users.json` treated as authoritative, rendering the *same* physical
|
||||
`users.json` treated as authoritative, rendering the _same_ physical
|
||||
`users.yml`. A writer whose own JSON was missing could not tell "nothing
|
||||
here yet" from "someone else's users", so it refused to write at all —
|
||||
which is exactly what a hive with existing users hit (#3422).
|
||||
|
|
@ -56,6 +56,6 @@ What still has to hold, since two processes share the file:
|
|||
rather than degrades, so both write paths fill in a synthetic address
|
||||
when none was supplied.
|
||||
|
||||
Neither restarts authelia: it watches the file. `swarmctl` *could* (it is
|
||||
Neither restarts authelia: it watches the file. `swarmctl` _could_ (it is
|
||||
root); this bridge deliberately cannot, and a reload that depends on which
|
||||
process wrote is not a reload.
|
||||
|
|
|
|||
Loading…
Reference in a new issue