How jzi96/tagwatch works
Tagwatch is a Go service that polls configured public container registries, tracks tag and digest changes in a persistent JSON baseline, optionally compares configured repositories with running Docker containers, and serves a server-rendered HTML report. The main workflow is configuration loading, registry snapshot collection and filtering, state/history updates, then report publication and HTTP rendering. Optional Docker inspection adds per-container comparisons. Edges reflect calls visible in the excerpts or capabilities explicitly documented in the README; unsampled implementation details are not inferred.
Main entry points: main.go Service entry · monitor.go Polling monitor · web.go HTTP handler · registry.go Registry client
Components 14
Startup and configuration
- Service entry
cmd/tagwatch/main.go - Configuration
internal/config/config.go
Registry tracking
- Polling monitor
internal/monitor/monitor.go - Registry client
internal/registry/registry.go - State and history
internal/monitor/state.go - JSON state file
Runtime comparison
- Docker inspector
internal/docker/docker.go - Running comparisons
internal/monitor/monitor.go
Report and web
- HTTP handler
internal/web/web.go - HTML report template
internal/web/index.html
Other components
- Operator
- Docker Engine
- OCI registries
- Report viewer
Connections 18
- Operator → Service entry: starts
README.md - Service entry → Configuration: loads settings
cmd/tagwatch/main.go - Service entry → Polling monitor: creates and runs
cmd/tagwatch/main.go - Service entry → Registry client: provides client
cmd/tagwatch/main.go - Service entry → Docker inspector: configures optionally
cmd/tagwatch/main.go - Service entry → HTTP handler: serves
cmd/tagwatch/main.go - Polling monitor → Configuration: parses and filters
internal/monitor/monitor.go - Polling monitor → Registry client: lists and resolves
internal/monitor/monitor.go - Registry client → OCI registries: requests tags and manifests
internal/registry/registry.go - Polling monitor → State and history: loads, applies, saves
internal/monitor/monitor.go - State and history → JSON state file: reads and writes
internal/monitor/state.go - Polling monitor → Running comparisons: builds report comparisons
internal/monitor/monitor.go - Running comparisons → Docker inspector: lists running containers
internal/monitor/monitor.go - Running comparisons → Registry client: resolves platform digest
internal/monitor/monitor.go - Docker inspector → Docker Engine: inspects over socket
internal/docker/docker.go - HTTP handler → Polling monitor: reads report
internal/web/web.go - HTTP handler → HTML report template: renders
internal/web/web.go - Report viewer → HTTP handler: requests report
README.md