---
title: Audit - firefox.yaml
description: Gremlin audit report 2026-04-03
published: true
date: 2026-04-03T02:51:09.611Z
tags: gremlin,audit
editor: markdown
dateCreated: 2026-04-03T02:51:09.611Z
---

# Audit Report — firefox.yaml

**Date:** 2026-04-03  
**File:** swarm/firefox.yaml  
**Type:** Docker Swarm  
**Verdict:** FAIL

---

**SWARM AUDIT**

1. **Homepage labels**: 
   - `homepage.group`: Remote Access (PASS)
   - `homepage.name`: Firefox (PASS)
   - `homepage.icon`: firefox.png (PASS)
   - `homepage.href`: https://firefox.netgrimoire.com (PASS)
   - `homepage.description`: Remote Browser (PASS)

2. **Uptime Kuma labels**: 
   - No Uptime Kuma labels found in the provided YAML file (FAIL). Ensure that any services running on this host have proper Uptime Kuma labels for visibility.

3. **Caddy labels on exposed services**:
   - `caddy=firefox.netgrimoire.com` (PASS)
   - `caddy.reverse_proxy=http://firefox:5800` (PASS)

4. **Placement constraints**: 
   - No placement constraints found in the provided YAML file (FAIL). Ensure that any critical services have proper placement constraints to meet availability requirements.

5. **Volumes use /DockerVol/<service> path convention**:
   - Volume path `/data/nfs/znas/Docker/firefox` does not follow the `/DockerVol/<service>` convention (FAIL). Volumes should be placed in a directory following this naming scheme for consistency and ease of management.

6. **Network references external netgrimoire overlay**: 
   - Network `netgrimoire` is referenced correctly and marked as external (PASS).

**VERDICT: FAIL**

- The YAML file lacks Uptime Kuma labels, which are essential for monitoring the status of services.
- No placement constraints are defined, which can lead to issues with service availability and redundancy.
- Volumes do not follow the recommended path convention, which may cause confusion and difficulty in managing storage resources.