Quantify Issues

Recent GitHub Issues Activity

_{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.}

Quantify commits

Quantified Commit Activity Over 30 Days

Developer	Avatar	Branches	PRs	Commits	Files	Changes
Andras Bacsai		3	33/33/0	122	189	6303
peaklabs-dev		3	30/29/5	60	48	3504
Luca		1	1/1/0	1	2	103
Eric Dahl		1	0/0/0	2	3	53
Alexandre Tolstenko		1	1/1/0	1	2	16
dependabot[bot]		2	3/3/0	2	2	16
JongChan Choi (Rieul)		1	1/1/0	1	1	5
Darren Sisson		1	3/2/0	1	1	5
Dmitry (dimaaan21)		1	1/1/0	1	1	4
Dennis Blume		1	1/1/0	1	1	2
Mr. Mendez		1	1/1/0	1	1	2
Nathanial Henniges		1	1/1/0	1	1	2
Gabriel Cossette		1	1/1/0	1	1	1
Nathan (Vahor)		0	7/7/0	0	0	0
Loukas Agorgianitis (agorgl)		0	1/1/0	0	0	0
Gabriel (galer7)		0	1/1/0	0	0	0
John Annunziato (ja3nyc)		0	1/0/0	0	0	0
Jay (mj-dcb)		0	0/1/0	0	0	0
nahuhh (nahuhh)		0	1/1/0	0	0	0
Loïc Tosser (wowi42)		0	1/1/0	0	0	0
Amit Yadav (Amitind)		0	2/0/0	0	0	0
Jonas (OG-Jons)		0	1/0/0	0	0	0
None (Telokis)		0	0/0/1	0	0	0
Giorgi Gagoshidze (ggagosh)		0	0/0/1	0	0	0
mufeng (iMuFeng)		0	1/0/0	0	0	0
Pjero Nizetic (nizetic)		0	1/0/0	0	0	0
Franck Kerbiriou (FranckKe)		0	1/1/0	0	0	0
Eric Dahl (Skeyelab)		0	2/2/1	0	0	0
alepouna (alepouna)		0	1/0/0	0	0	0
lasse (lassejlv)		0	1/1/0	0	0	0
Marek Mahanský (mahansky)		0	1/1/0	0	0	0
Lucas (mirsella)		0	0/0/1	0	0	0
Peter Kellner (pkellner)		0	1/1/0	0	0	0
Fenz0 (theraays)		0	1/0/1	0	0	0
Luis Daniel (danielqba)		0	1/1/0	0	0	0
Matt Stein (mattstein)		0	2/2/0	0	0	0
None (ALsJourney)		0	1/0/0	0	0	0
Tim (TimKochDev)		0	1/1/0	0	0	0
Valentinas Čirba (fizikiukas)		0	1/1/0	0	0	0
Nicco (cupcakearmy)		0	2/0/1	0	0	0
Grant Magdanz (grantmagdanz)		0	1/1/0	0	0	0
Bohdan Shulha (bohdan-shulha)		0	0/1/0	0	0	0
Julien Beugras (julienbeugras)		0	1/1/0	0	0	0
Tiago Miguel (tiagomiguel29)		0	0/1/0	0	0	0
Nicolas Stuhlfauth (nicostuhlfauth)		0	1/0/0	0	0	0
Valentin Schabschneider (valentinschabschneider)		0	0/1/0	0	0	0

_{PRs: created by that dev and opened/merged/closed-unmerged during the period}

Report On: Fetch issues

Recent Activity Analysis

The Coolify project has seen a substantial amount of recent activity, with 324 open issues currently reported. Notably, many of these issues are categorized as bugs, indicating potential instability or usability concerns within the platform. There is a significant focus on deployment issues, particularly with Docker and Nixpacks, which suggests that users are experiencing challenges in getting their applications to run smoothly.

A recurring theme among the issues is related to environment variables and configuration management, with users reporting problems such as variables not being passed correctly or being overridden unexpectedly. Additionally, there are multiple reports of health check failures and deployment timeouts, which could indicate underlying performance issues or misconfigurations in the deployment pipeline.

Issue Details

Recent Issues

1. Issue #3553: [Bug]: API Healthcheck does not work

   • Priority: 🐛 Bug
   • Status: Open
   • Created: 0 days ago
   • Update: N/A

2. Issue #3552: [Bug]: ERR_SSL_UNRECOGNIZED_NAME_ALERT

   • Priority: 🐛 Bug
   • Status: Open
   • Created: 0 days ago
   • Update: N/A

3. Issue #3549: [Bug]: no configuration file provided: not found

   • Priority: 🐛 Bug
   • Status: Open
   • Created: 0 days ago
   • Update: N/A

4. Issue #3548: [Bug]: 500 error

   • Priority: 🐛 Bug
   • Status: Open
   • Created: 0 days ago
   • Update: N/A

5. Issue #3544: [Bug]: Gitlab - failed to read /data/coolify/services/...

   • Priority: 🐛 Bug
   • Status: Open
   • Created: 1 day ago
   • Update: N/A

6. Issue #3541: [Bug]: dragonfly terminal return (error) NOAUTH Authentication required.

   • Priority: 🐛 Bug
   • Status: Open
   • Created: 2 days ago
   • Update: N/A

7. Issue #3537: [Bug]: Build server + Git, latest image not pulled

   • Priority: 🐛 Bug
   • Status: Open
   • Created: 2 days ago
   • Update: N/A

8. Issue #3534: [Bug]: Environment variables not replaced in source compose file.

   • Priority: 🐛 Bug, 🚧 Next, 🐞 Confirmed Bug
   • Status: Open
   • Created: 3 days ago
   • Update: N/A

9. Issue #3533: [Bug]: Bad Gateway when add new resource

   • Priority: 🐛 Bug
   • Status: Open
   • Created: 3 days ago
   • Update: N/A

10. Issue #3532: [Bug]: v4.0.0-beta.341 won't take environment variable in consideration when (re)deploying

    • Priority: 🐛 Bug, 🐞 Confirmed Bug
    • Status: Open
    • Created: 3 days ago
    • Update: N/A

Analysis of Themes and Commonalities

• The majority of recent issues revolve around bugs related to deployment processes, particularly with Docker and Nixpacks.
• A significant number of users are facing problems with environment variables not being set or recognized correctly during deployments.
• Health check failures and errors related to SSL connections are also prevalent, indicating potential networking or configuration issues.
• Users have reported that changes made to configurations do not persist or are overridden unexpectedly.

This pattern suggests that while Coolify provides powerful features for application deployment, there may be critical areas requiring attention to enhance stability and user experience.

Report On: Fetch pull requests

Overview

The analysis of the pull requests (PRs) for the Coolify project reveals a vibrant and active development community focused on enhancing the platform's functionality, security, and user experience. The PRs cover a wide range of improvements from bug fixes and feature additions to security enhancements and performance optimizations.

Summary of Pull Requests

• PR #3551: Fix: Proxy issues - Addresses multiple proxy-related issues, improving performance and reliability.
• PR #3550: v4.0.0-beta.343 - Fixes parsing special environment variables and updates service statuses in the database.
• PR #3545: Feat: Improve Docker cleanup - Adds manual trigger for Docker cleanup and options for unused volume and network deletion.
• PR #3542: Fix: Volume issues in development - Introduces breaking changes for development setups to fix volume-related issues.
• PR #3518: [WIP] Refactor: Improve seeders - A work-in-progress PR aimed at simplifying seeders management.
• PR #3515: Add template for HeyForm - Adds a new service template for HeyForm.
• PR #3503: Add Template for cal.com - Introduces a new template for deploying cal.com as a service.
• PR #3490: Feat: Improve release.md - Enhances the release guide to reduce support requests related to versioning and release frequency.
• PR #3446: feat: add immich service - Adds support for the immich service.
• PR #3435: Add kimai template - Introduces a new template for kimai.

Analysis of Pull Requests

The PRs reflect ongoing efforts to expand Coolify's capabilities by adding support for new services and improving existing features. Notably, PRs like #3545 and #3542 indicate a focus on enhancing operational efficiency through better Docker management and development environment setup.

Security is also a priority, as seen in PRs like #3551, which addresses potential vulnerabilities related to proxy configurations. This aligns with the project's commitment to providing a secure self-hosting solution.

The presence of multiple PRs related to templates (#3515, #3503, #3435) suggests an active community contribution towards making Coolify more versatile by supporting a wider array of applications.

The project's responsiveness to community feedback is evident from PRs like #3490, which aims to clarify release processes based on user inquiries.

Overall, the pull request activity indicates a healthy project lifecycle with continuous improvements driven by both core developers and community contributors. The focus on security, operational efficiency, and expanding service support highlights Coolify's commitment to being a robust alternative to traditional cloud platforms.

Report On: Fetch commits

Repo Commits Analysis

Development Team and Recent Activity

Team Members

• Andras Bacsai (andrasbacsai)

• peaklabs-dev

• Luca-Sordetti

• gabrielcossette

• tolstenko

• nathanialhenniges

• djsisson

• JustMrMendez

• dennisblume

• dependabot[bot]

• disjukr

• EricDahl-NotreDame

• dimaaan21

Recent Activities

Andras Bacsai

• Commits: 122
• Changes: 6303 across 189 files
• Recent Work:
  • Merged multiple pull requests including updates to the cloudflare configuration, Docker commands, and cleanup commands.
  • Refactored various components for improved performance and readability.
  • Fixed issues related to cloudflare tunnels, SSH key management, and database migrations.
  • Collaborated with peaklabs-dev on several features and fixes.

peaklabs-dev

• Commits: 60
• Changes: 3504 across 48 files
• Recent Work:
  • Contributed to fixing SSH multiplexing issues and cloudflare configurations.
  • Merged several pull requests related to documentation updates and feature enhancements.

Luca-Sordetti

• Commits: 1
• Changes: 103 across 2 files
• Recent Work:
  • Added an API endpoint to execute a command.

gabrielcossette

• Commits: 1
• Changes: 1 across 1 file
• Recent Work:
  • Fixed Ghost Template domain generation.

tolstenko

• Commits: 1
• Changes: 16 across 2 files
• Recent Work:
  • Added hints for environment variable checks.

nathanialhenniges

• Commits: 1
• Changes: 2 across 1 file
• Recent Work:
  • Updated documentation with links for more services.

djsisson

• Commits: 1
• Changes: 5 across 1 file
• Recent Work:
  • Updated cloudflared.yaml for better compatibility.

JustMrMendez

• Commits: 1
• Changes: 2 across 1 file
• Recent Work:
  • Fixed deployment issues related to database alterations.

dennisblume

• Commits: 1
• Changes: 2 across 1 file
• Recent Work:
  • Fixed WebSocket connection issues when using Caddy.

dependabot[bot]

• Commits: 2
• Changes: 16 across 2 files
• Recent Work:
  • Updated dependencies including rollup.

disjukr, EricDahl-NotreDame, dimaaan21

Each contributed minor changes or fixes within their respective commits.

Patterns and Themes

1. High Activity from Andras Bacsai: Dominates commit count and changes, indicating a lead role in development.
2. Collaborative Efforts: Frequent merges between team members suggest active collaboration on features and bug fixes.
3. Focus on Refactoring: A significant number of commits involve refactoring existing code for improved performance and maintainability.
4. Feature Enhancements: New features such as API endpoints and configuration improvements are being actively developed.
5. Community Contributions: Engagement from various contributors indicates a healthy community involvement in the project.

Conclusion

The development team is actively engaged in enhancing the Coolify platform with significant contributions from key members. The focus on refactoring, feature enhancements, and collaborative efforts reflects a strong commitment to improving the project's functionality and user experience.