I've commented out Caddy in the docker-compose.yaml file and included a message describing the security vulnerabilities associated with enabling it.

deployment/docker/docker-compose.yaml

@@ -127,19 +127,20 @@ services:
     <<: *knightcrawler-app
     networks:
       - knightcrawler-network
-    
-  caddy:
-    image: caddy:latest
-    restart: unless-stopped
-    ports:
-      - "80:80"
-      - "443:443"
-      - "443:443/udp"
-    volumes:
-      - ./Caddyfile:/etc/caddy/Caddyfile
-      - ./site:/srv
-      - caddy_data:/data
-      - caddy_config:/config
+
+# Remove the #'s to activate Caddy for external access. Please note that this action may pose security vulnerabilities and potential damage for which Knightcrawler and its contributors cannot be held responsible.
+#  caddy:
+#    image: caddy:latest
+#    restart: unless-stopped
+#    ports:
+#      - "80:80"
+#      - "443:443"
+#      - "443:443/udp"
+#    volumes:
+#      - ./Caddyfile:/etc/caddy/Caddyfile
+#      - ./site:/srv
+#      - caddy_data:/data
+#      - caddy_config:/config
       
 networks:
   knightcrawler-network: