2 KiB
2 KiB
| title | description | published | date | tags | editor | dateCreated |
|---|---|---|---|---|---|---|
| Audit - filebrowser.yaml | Gremlin audit report 2026-04-20 | true | 2026-04-20T11:12:31.873Z | gremlin,audit | markdown | 2026-04-20T11:12:31.873Z |
Audit Report — filebrowser.yaml
Date: 2026-04-20
File: swarm/filebrowser.yaml
Type: Docker Swarm
Verdict: PASS
Audit Report for swarm/filebrowser.yaml
-
Homepage labels: All homepage labels are present.
homepage.group=Jolly Rogerhomepage.name=FileBrowserhomepage.icon=filebrowser.pnghomepage.href=http://filebrowser.netgrimoire.comhomepage.description=Web-based file manager
-
Uptime Kuma labels: Both Uptime Kuma labels are present.
kuma.filebrowser.http.name="FileBrowser"kuma.filebrowser.http.url=http://filebrowser:80
-
Caddy labels on exposed services:
caddy=filebrowser.netgrimoire.comcaddy.import=authentikcaddy.reverse_proxy="{{upstreams 80}}"– Issue: This label references a variable that is not explicitly defined in the YAML. It should be replaced with the actual upstream service name or IP. Fix: Replace{{upstreams 80}}with the appropriate upstream service name or IP.
-
Placement constraints: The constraint checks for
node.labels.general == true, but it does not specify a label to check against, which might lead to unintended placement if no such label is set on any node.- Fix: Ensure that there is a label set on nodes like
general=trueor modify the constraint to match an existing label.
- Fix: Ensure that there is a label set on nodes like
-
Volumes use /DockerVol/ path convention:
- The volumes are correctly using the
/data/nfs/Baxter/Docker/filebrowser/directory, which does not follow the/DockerVol/<service>convention. Fix: Modify the volume paths to conform to the specified convention, for example,volumes: - /DockerVol/filebrowser/config:/config.
- The volumes are correctly using the
-
Network references external netgrimoire overlay:
- The network
netgrimoireis correctly referenced and is set as external.
- The network
VERDICT: FAIL