nginx-proxy/docker-gen
Docker Gen
docker-gen is a general-purpose configuration generator that produces configuration files by applying Go templates to live Docker container metadata. It generates dynamic configuration for reverse proxies, log forwarding, log rotation, and other service files based on real-time container state.
The tool watches Docker container lifecycle events—such as start, stop, and die—and automatically re-renders templates each time a change occurs. It supports multiple template jobs defined in a configuration file, executing them sequentially, and can send Unix signals or run commands after regeneration to reload dependent processes. Container filtering via labels, status, or port exposure ensures only relevant containers participate in template generation.
Beyond reverse proxy configuration, docker-gen automates the creation of Fluentd log forwarding entries and logrotate configuration files derived from container metadata and environment variables. Its template-based approach makes it adaptable to any text-based configuration format, enabling integration with a wide variety of services that need dynamic, container-aware configuration.
The project is written in Go and distributed as a single binary, with templates and generated outputs stored as plain files on disk.
Features
- Container Event Driven Template Engines - Automatically regenerates container configuration files in response to container lifecycle events.
- Template-Driven Generation Engines - Automatically re-renders templates by monitoring Docker container lifecycle events.
- Go Template Rendering - Applies Go text/template engine to live container metadata for dynamic configuration generation.
- Live Container Metadata Renderers - Applies Go templates to live Docker container metadata to produce dynamic configuration files for various services.
- Container Metadata Configuration Generators - Generates configuration files from live Docker container metadata using user-defined templates.
- Container Lifecycle Triggered File Regenerations - Monitors Docker container lifecycle events to automatically re-render template files.
- Event-Driven Triggers - Monitors container lifecycle events to automatically regenerate configuration and trigger external commands.
- Reverse Proxy Configurations - Generates reverse proxy configuration files from container environment variables mapping virtual hosts to endpoints.
- Dynamic Reverse Proxy Config Generators - Automatically renders reverse proxy configuration files by mapping container environment variables to virtual host endpoints.
- Multiple Template Job Pipelines - Generates dynamic configuration by executing a pipeline of template jobs defined in a single configuration file.
- Logrotate - Generates logrotate configuration files from container metadata for automated log rotation.
- Sequential Multi-Job Template Executors - Defines multiple template jobs in a configuration file and executes them sequentially for automated configuration generation.
- Log Rotation Config Generators - Automatically generates logrotate configuration files from container metadata for log rotation.
- Container Selection Filters - Filters containers based on labels, status, or port exposure to selectively include them in template generation.
- Label-Based Selection - Filters containers by Docker labels, status, or port exposure to selectively include them in template generation.
- Log Rotation Configuration Generators - Produces logrotate configuration files based on container metadata for automated log rotation.
- Log Forwarders - Generates configuration entries to tail and forward container logs to centralized aggregation systems.
- Log Forwarder Configuration Generators - Generates Fluentd configuration entries to tail and forward container logs to centralized systems.
Star history
How this analysis was created: This summary and feature list were written by an AI model that read the project's README and public documentation pages. Each feature links to the documentation it came from; stars, license and language come straight from the GitHub API. The model does not read the source code, and the analysis is refreshed when the project is re-analysed. Learn more on our About page.
