Dokku, a Docker-powered Platform as a Service (PaaS), continues to prioritize dependency updates and bug fixes, though older pull requests remain unresolved, indicating potential resource constraints or prioritization challenges.
Recent activities in the Dokku project reveal an emphasis on maintaining up-to-date dependencies, as evidenced by numerous pull requests generated by Dependabot. The project aims to ensure security and compatibility with the latest versions of libraries and tools. Notable pull requests include updates to github.com/onsi/gomega (#7096, #7094) and google.golang.org/grpc (#7090), alongside bug fixes such as handling parent PID issues in LXD VMs (#7088). However, older pull requests, some open for nearly a year, suggest bottlenecks in reviewing and merging contributions.
Recent issues and pull requests highlight ongoing development and user engagement, with a focus on improving environment variable management and configuration handling. Key issues include problems with nginx configuration post-app cloning and health check deployment tasks. The development team has been active in addressing these challenges:
Summary
Quantified Reports
Detailed Reportsdokku-image-size-limit plugin.Overall, while Dokku demonstrates active maintenance through dependency updates and bug fixes, attention to older unresolved pull requests is necessary to prevent stagnation in certain development areas.
| Timespan | Opened | Closed | Comments | Labeled | Milestones |
|---|---|---|---|---|---|
| 7 Days | 7 | 1 | 8 | 0 | 1 |
| 30 Days | 12 | 6 | 28 | 0 | 1 |
| 90 Days | 32 | 12 | 83 | 1 | 2 |
| 1 Year | 122 | 87 | 423 | 2 | 5 |
| All Time | 2698 | 2650 | - | - | - |
Like all software activity quantification, these numbers are imperfect but sometimes useful. Comments, Labels, and Milestones refer to those issues opened in the timespan in question.
| Developer | Avatar | Branches | PRs | Commits | Files | Changes |
|---|---|---|---|---|---|---|
| Jose Diaz-Gonzalez |  |
3 | 8/5/1 | 17 | 72 | 1633 |
| Dokku Bot |  |
1 | 0/0/0 | 2 | 56 | 639 |
| dependabot[bot] |  |
11 | 51/39/6 | 47 | 27 | 321 |
| Ben Katz |  |
1 | 2/1/0 | 2 | 1 | 4 |
| Tasos Maschalidis |  |
1 | 1/1/0 | 1 | 1 | 2 |
| Tim de Koning (Reggino) | 0 | 0/1/0 | 0 | 0 | 0 | |
| None (andreby) | 0 | 1/0/0 | 0 | 0 | 0 | |
| Flavio Poletti (polettix) | 0 | 0/1/0 | 0 | 0 | 0 | |
| Muma (DavidTheProgrammer) | 0 | 0/1/0 | 0 | 0 | 0 |
PRs: created by that dev and opened/merged/closed-unmerged during the period
The Dokku project currently has 48 open issues on GitHub, with a notable uptick in recent activity. Several issues are related to bugs and enhancements, indicating ongoing development and user engagement. A recurring theme is the need for better handling of environment variables and configuration management, particularly in relation to Docker image deployments and build processes.
Notable complications include issues with the nginx configuration not being generated correctly after app cloning, as well as problems related to the handling of health checks and deployment tasks. There are also several instances where users have reported errors stemming from outdated dependencies or misconfigurations following upgrades.
Issue #7093: network:info does not appear to do anything
Issue #7092: Adding app name to dokku apps:report
Issue #7089: dokku domain:set error: [sudo] password for dokku
Issue #7083: Nginx: runsv not running
Issue #7082: dokku.prerm will loop forever in ps_backtrace() because $ppid == 0
Issue #7081: Deploy fails "listening on ports" healthcheck
Issue #7061: Disk space usage: Disk when full many deployments in same day
Issue #7018: Manual steps when upgrading dokku?
Issue #6998: Dokku ps:retire (or cron job) trying to retire running app
Issue #6990: SSL_SERVER_NAME not populated even though ssl is set up for vhost
Several issues highlight a lack of clarity in how environment variables are managed during the build process, particularly with Docker images. Users frequently encounter problems with missing or incorrectly configured environment variables, which can lead to failed deployments or unexpected behavior.
Additionally, there are multiple reports regarding the handling of nginx configurations during app cloning and upgrades, suggesting that improvements are needed in how these configurations are generated and maintained.
The ongoing discussions about support for newer versions of Ubuntu and Debian also indicate a need for the project to keep pace with changes in underlying operating systems, which can affect compatibility and functionality.
Overall, the current issue landscape reflects both the active engagement of users seeking enhancements and the challenges they face in managing their applications within the Dokku ecosystem.
The dokku/dokku repository currently has 16 open pull requests, primarily focused on dependency updates and minor enhancements. The majority of these pull requests are created by Dependabot, indicating an active effort to keep the project up-to-date with the latest versions of its dependencies.
PR #7096: Bumps github.com/onsi/gomega from 1.34.1 to 1.34.2 in /plugins/config. This is a maintenance update requiring Go 1.22+.
PR #7094: Similar to PR #7096, this also bumps github.com/onsi/gomega from 1.34.1 to 1.34.2 but in /plugins/common.
PR #7090: Updates google.golang.org/grpc from 1.65.0 to 1.66.0 in /tests/apps/gogrpc, introducing new features and bug fixes.
PR #7088: Fixes an issue related to handling parent PID being 0 inside an LXD VM, closing issue #7082.
PR #7086: Bumps timberio/vector from 0.39.0-debian to 0.40.1-debian in /plugins/logs.
PR #7085: Updates watchdog from 4.0.2 to 5.0.0, introducing breaking changes that drop support for Python 3.8.
PR #7084: Bumps zipp from 3.20.0 to 3.20.1 in /docs/_build.
PR #7079: Updates pyparsing from 3.1.2 to 3.1.4, fixing a regression affecting Python 3.6 installs.
PR #7077: Adds a cron dependency necessary for running scheduled cron jobs, addressing deployment issues.
PR #7076: Bumps mvdan.cc/sh/v3 from 3.8.0 to 3.9.0 in /plugins/cron, dropping support for Go 1.21.
PR #7075: Upgrades the herokuish builder to gliderlabs/herokuish:latest-24.
PR #7074: Upgrades the CNB builder to heroku/builder:24, closing issue #6994.
PR #7035: Bumps traefik from 2.11.2 to 3.1.x in /plugins/traefik-vhosts.
14-16: A series of older PRs (#6223, #6716, and others) addressing various enhancements and bug fixes, some of which have been open for extended periods (up to nearly a year).
The recent pull requests predominantly focus on updating dependencies across various components of the Dokku project, reflecting a proactive approach to maintain security and compatibility with newer versions of libraries and tools used within the platform.
Dependency Management: A significant number of pull requests are generated by Dependabot, indicating that the project is actively managing its dependencies and ensuring they are kept up-to-date with the latest releases.
Bug Fixes and Enhancements: Several PRs address specific bugs or enhance existing functionality (e.g., handling parent PID issues in LXD VMs). This highlights ongoing efforts to improve the stability and usability of Dokku.
Documentation Improvements: There are also PRs aimed at improving documentation clarity, such as correcting links or adding missing information about plugins and configurations.
Old Pull Requests: Some older pull requests remain open for extended periods (e.g., PR #6223 has been open for over a year). This could indicate a lack of resources or prioritization issues within the development team, potentially leading to stagnation on certain features or fixes.
Lack of Merge Activity on Older PRs: The presence of numerous open PRs alongside a history of recent merges suggests that while there is active development happening, there may be bottlenecks in reviewing and merging contributions from the community or even internal contributors.
The repository has seen a healthy amount of merge activity recently, particularly concerning dependency updates and minor enhancements aimed at improving overall functionality and security posture (e.g., upgrading Go versions). However, the presence of many open PRs indicates that while some areas are actively being addressed, others may require more attention.
Overall, dokku/dokku demonstrates an active development environment with a strong focus on maintaining up-to-date dependencies and addressing bugs promptly while also enhancing documentation for better user guidance. However, attention should be given to older pull requests that remain unresolved to ensure continuous improvement without stagnation in certain areas of development.
Jose Diaz-Gonzalez (josegonzalez)
gunicorn, django, and various Go modules.Dependabot[bot]
werkzeug, mkdocs-material, and gomega.Tasos Maschalidis (Tashows)
dokku-image-size-limit plugin.Ben Katz (bakatz)
Flavio Poletti (polettix)
Overall, the recent activities reflect a committed team focused on improving the Dokku platform through regular updates, bug fixes, and enhanced documentation.