From 8f8c138c889da7383541194d53615d83dfed8c18 Mon Sep 17 00:00:00 2001 From: Jay Date: Wed, 10 Jun 2026 22:44:49 +0200 Subject: [PATCH] [Traccar] refactor: Remove redundant dokploy-network declaration Dokploy attaches its own network automatically on deploy, so declaring dokploy-network in the compose file is redundant. Drop it from the traccar service and update its README. Also fold traccar into the list of examples in CLAUDE.md now that it follows the convention. Co-Authored-By: Claude Opus 4.8 (1M context) --- CLAUDE.md | 3 +-- traccar/README.md | 3 ++- traccar/docker-compose.yml | 6 ------ 3 files changed, 3 insertions(+), 9 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index 0f5418f..fb3eeef 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -34,8 +34,7 @@ exposure declare and connect to this network. Services that don't need Cloudflare exposure should **not** declare any network in their compose file — Dokploy attaches its own `dokploy-network` automatically on deploy (e.g. `n8n`, -`plex`, `watchtower`). `traccar` predates this and still -declares `dokploy-network` explicitly, which is redundant. +`plex`, `traccar`, `watchtower`). **Container management:** Watchtower handles automatic image updates using label-based opt-in diff --git a/traccar/README.md b/traccar/README.md index 2f0d61c..80e47b3 100644 --- a/traccar/README.md +++ b/traccar/README.md @@ -12,7 +12,8 @@ ports. ## Networks -Connects to `dokploy-network` (external, managed by Dokploy). +No network is declared in the compose file — Dokploy +attaches its own network automatically on deploy. ## Notes diff --git a/traccar/docker-compose.yml b/traccar/docker-compose.yml index 3b33033..2db85f8 100644 --- a/traccar/docker-compose.yml +++ b/traccar/docker-compose.yml @@ -5,8 +5,6 @@ services: restart: unless-stopped security_opt: - no-new-privileges:true - networks: - - dokploy-network ports: - 25002:5013 - 25003:5023 @@ -21,7 +19,3 @@ services: max-file: "3" labels: - com.centurylinklabs.watchtower.enable=true - -networks: - dokploy-network: - external: true