nginx-proxy/docker-gen

Generate files from docker container meta-data

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 hour ago
Added to GitGenius on September 14th, 2026
Created on March 14th, 2014
Open Issues & Pull Requests: 30 (+0)
GitHub issues: Enabled
Number of forks: 609
Total Stargazers: 4,630 (+0)
Total Subscribers: 80 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 85.4 days
Mean response time: 1062.0 days
90th percentile: 3538.2 days
Tracked items: 37

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 3,953 days
Stale 30+ days: 2
Stale 90+ days: 2

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (3)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

docker-gen is a file generator that renders templates using Docker container metadata.

The tool solves the problem of dynamically configuring applications that need to adapt to changing container deployments. It watches the Docker daemon for container events and regenerates configuration files by applying Go templates to container metadata. This enables automatic updates to reverse proxy configs, logging configurations, service discovery scripts, and other files without manual intervention when containers start, stop, or change.

The tool suits operators managing containerized infrastructure who need tight integration between container lifecycle events and application configuration. It works well for centralized logging setups using fluentd or logstash, log rotation with logrotate, reverse proxy configuration for nginx or haproxy, and service discovery with etcd or similar systems. docker-gen can be deployed in three ways: directly on the host, bundled inside a container alongside other applications, or as a separate standalone container. The separate container approach is useful when you want to avoid exposing the Docker socket to publicly accessible services.

The project maintains a steady stream of commits addressing bug fixes and feature improvements. Pull requests receive timely review and integration. The maintainers actively respond to issues and incorporate community contributions. Development activity shows consistent engagement with the codebase and responsiveness to user needs.