Coolify, an open-source platform for self-hosting applications, continues to experience significant user-reported deployment issues, particularly with Docker configurations and external service integrations, despite ongoing development efforts.
The project aims to provide an alternative to cloud services like Heroku by allowing users to manage their servers and applications on their own hardware. It is actively maintained with a strong community presence, as evidenced by its high number of stars and forks on GitHub.
Recent issues highlight recurring problems with deployment failures, environment variable management, and integration with services such as GitHub. Notable issues include #3220 regarding server connectivity (504 Gateway Time-out) and #3218 concerning unwanted app restarts. These indicate potential areas where the platform's reliability could be improved.
Andras Bacsai (andrasbacsai)
Summary
Quantified Reports
Detailed ReportsparseDockerComposeFile.Stuart Rowlands (stooit)
Telokis
Peaklabs-dev (ayntk-ai)
Gabriel Peralta (kunumigab)
Alexzvn
Jonathan Müller (J-o-n-a-t-h-a-n-M-u-e-l-l-e-r)
Filip Gornitzka Abelson (filiabel)
High Volume of Open Issues: With 269 open issues, many users report challenges with deployment and configuration management, suggesting a need for enhanced documentation or tooling improvements.
Service Template Expansion: Numerous pull requests focus on adding new service templates, indicating a strategic push to broaden the platform's capabilities.
Dominant Contributor: Andras Bacsai leads development efforts significantly, contributing the majority of recent commits, which may impact project direction and decision-making dynamics.
Collaborative Environment: Despite the dominance of a single contributor, there is active collaboration among team members, fostering a diverse contribution landscape.
Testing Emphasis: The introduction of tests alongside new features reflects a commitment to maintaining code quality and reliability through robust testing practices.
| Timespan | Opened | Closed | Comments | Labeled | Milestones |
|---|---|---|---|---|---|
| 7 Days | 10 | 38 | 9 | 6 | 1 |
| 30 Days | 74 | 69 | 141 | 40 | 1 |
| 90 Days | 389 | 196 | 1016 | 276 | 1 |
| All Time | 1552 | 1283 | - | - | - |
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 |
|---|---|---|---|---|---|---|
| Andras Bacsai |  |
2 | 5/5/0 | 114 | 163 | 15009 |
| ayntk-ai |  |
1 | 18/2/5 | 19 | 11 | 468 |
| Telokis |  |
1 | 4/1/0 | 1 | 1 | 112 |
| Gabriel Peralta |  |
1 | 1/1/0 | 2 | 2 | 49 |
| Filip Gornitzka Abelson |  |
1 | 1/1/0 | 1 | 1 | 48 |
| Alexzvn |  |
1 | 1/1/0 | 2 | 1 | 45 |
| Luan Estradioto (LEstradioto) | 1 | 2/2/0 | 1 | 1 | 14 | |
| Stuart Rowlands |  |
1 | 1/1/0 | 1 | 1 | 2 |
| Jonathan Müller |  |
1 | 2/1/1 | 1 | 1 | 2 |
| Nicolas Bondoux (Nsbx) | 0 | 1/0/1 | 0 | 0 | 0 | |
| Kaotic (Kaotic) | 0 | 0/1/0 | 0 | 0 | 0 | |
| Toby Brancher (Loque-) | 0 | 0/1/0 | 0 | 0 | 0 | |
| Sylvain Autran (Pilpin) | 0 | 2/0/0 | 0 | 0 | 0 | |
| Givan (givanz) | 0 | 1/0/0 | 0 | 0 | 0 | |
| Jay (mj-dcb) | 0 | 1/0/0 | 0 | 0 | 0 | |
| 8x4 (8times4) | 0 | 1/0/0 | 0 | 0 | 0 | |
| Giorgi Gagoshidze (ggagosh) | 0 | 1/0/0 | 0 | 0 | 0 | |
| Peter Tran (nekomi2) | 0 | 1/0/0 | 0 | 0 | 0 | |
| Franck Kerbiriou (FranckKe) | 0 | 4/0/0 | 0 | 0 | 0 | |
| Eric Dahl (Skeyelab) | 0 | 1/0/0 | 0 | 0 | 0 | |
| Darren Sisson (djsisson) | 0 | 3/1/1 | 0 | 0 | 0 | |
| Lucas (mirsella) | 0 | 1/0/0 | 0 | 0 | 0 | |
| Alexander G. (rennokki) | 0 | 1/0/0 | 0 | 0 | 0 | |
| None (sroepges) | 0 | 1/0/0 | 0 | 0 | 0 | |
| Maximilian Pluskat (Seiikatsu) | 0 | 1/0/0 | 0 | 0 | 0 | |
| Stoufiler (Stoufiler) | 0 | 0/0/1 | 0 | 0 | 0 | |
| busybox (busybox11) | 0 | 1/1/0 | 0 | 0 | 0 | |
| Matt (OhThatMatt) | 0 | 3/2/0 | 0 | 0 | 0 | |
| None (nullishamy) | 0 | 1/0/0 | 0 | 0 | 0 | |
| Juan Felipe [Married Games] (JuanxCursed) | 0 | 1/0/0 | 0 | 0 | 0 | |
| Bohdan Shulha (bohdan-shulha) | 0 | 1/0/0 | 0 | 0 | 0 | |
| Code Wizard (pieter-berkel) | 0 | 1/0/1 | 0 | 0 | 0 | |
| Tiago Miguel (tiagomiguel29) | 0 | 1/0/0 | 0 | 0 | 0 | |
| Christian Kolbow (christiankolbow) | 0 | 8/0/3 | 0 | 0 | 0 | |
| Jonathan Reisdorf (jonathan-reisdorf) | 0 | 1/1/0 | 0 | 0 | 0 | |
| Lorenzo Migliorero (lorenzomigliorero) | 0 | 0/1/0 | 0 | 0 | 0 | |
| Valentin Schabschneider (valentinschabschneider) | 0 | 1/0/0 | 0 | 0 | 0 |
PRs: created by that dev and opened/merged/closed-unmerged during the period
The Coolify project has been experiencing a high volume of activity with 269 open issues, indicating ongoing user engagement and a variety of challenges being reported. Notably, many issues are related to deployment failures, environment variable management, and integration problems with external services like GitHub and Supabase.
Several issues exhibit recurring themes, such as problems with health checks failing for various applications, difficulties in managing environment variables, and complications arising from Docker configurations. The presence of multiple reports regarding SSL certificate issues and network configurations suggests that users are facing significant hurdles in setting up their applications correctly.
Issue #3220: [Bug]: 504 Gateway Time-out when validating server
Issue #3218: [Bug]: dont start app when app explicitly stopped
Issue #3211: [Bug]: Invite links via E-Mail not working
Issue #3209: [Bug]: Unable to Identify github_app_uuid for Deploying Private Repository via Coolify API
Issue #3196: [Bug]: Force Deploy without Cache only works when the project is stopped!
Issue #3191: [Bug]: column "image" of relation "service_applications" does not exist
Issue #3189: [Bug]: WordPress and ClassicPress with MySQL have no ARM image
Issue #3150: [Bug]: /artifacts/build.sh times out attempting to load .dockerignore & Dockerfile
Issue #3126: [Bug]: Cannot share a volume between services in docker-compose
Issue #3114: [Bug]: "Preserve Repository During Deployment" option has trouble with directories
504 Gateway Time-out (#3220) indicates potential server connectivity problems that could affect user experience significantly.The recurring themes across these issues suggest that users are struggling primarily with:
These challenges could imply a need for improved documentation, more robust error handling within the application, and potentially a reevaluation of how certain features are implemented to enhance user experience and reliability.
In summary, while Coolify is actively maintained and has a vibrant community, addressing these persistent issues will be crucial for maintaining user trust and satisfaction as the platform continues to grow.
The analysis of the pull requests (PRs) for the Coolify project reveals a total of 73 open PRs, with a significant focus on adding new service templates, fixing bugs, and enhancing existing features. The activity indicates a vibrant development environment with ongoing contributions from multiple developers.
PR #3219: Add Vvveb CMS template
PR #3216: Fix install.sh to use the correct port
PR #3215: Avoid crash if the team is not set
PR #3214: Add FreshRSS service template
PR #3213: Add Traccar template
PR #3202: Add Mailpit template
PR #3201: Add Plunk template
PR #3199: Add Nextcloud with Postgres template
PR #3198: Update Authentik
PR #3194: Add CloudBeaver template
The current state of open pull requests in the Coolify repository reflects several key themes and trends:
Service Template Additions: A significant number of PRs focus on adding new service templates (e.g., Vvveb CMS, FreshRSS, Traccar). This trend indicates an ongoing effort to expand the platform's capabilities and provide users with more options for self-hosted applications. The contributions are diverse, showcasing various developers' interests and expertise in different technologies.
Bug Fixes and Enhancements: Several PRs aim to fix existing issues or enhance functionality (e.g., correcting installation scripts, avoiding crashes). This reflects a commitment to maintaining code quality and improving user experience. Notably, PRs like #3215 highlight proactive measures taken to address previously reported bugs, which is essential for fostering community trust and satisfaction.
Community Engagement and Collaboration: The involvement of multiple contributors suggests a healthy collaborative environment within the project. Developers are actively engaging with one another through comments and discussions on PRs, which can lead to improved code quality through peer reviews and shared knowledge.
Old PRs and Merge Activity: While there is a robust influx of new PRs, it’s important to monitor older PRs that may not have received attention recently. The lack of merge activity on some older submissions could indicate potential bottlenecks in the review process or prioritization challenges within the development team.
Documentation and User Guidance Improvements: Many recent PRs include updates to documentation alongside code changes (e.g., PRs #3214, #3202). This practice is crucial as it ensures that users can easily understand how to implement new features or troubleshoot issues effectively.
Anomalies in Recent Activity: There are instances where certain PRs have been marked as drafts or closed without merging (e.g., PR #2998). These decisions should be communicated clearly to contributors to maintain transparency regarding project direction and priorities.
In conclusion, the current landscape of pull requests for Coolify showcases active development focused on expanding functionality through new service templates while addressing existing issues through bug fixes and enhancements. Continued engagement from contributors will be vital in sustaining this momentum and ensuring that the platform remains responsive to user needs and technological advancements.
parseDockerComposeFile function.stooit, Telokis, peaklabs-dev, and others.Dominance of Andras Bacsai: The majority of commits (114 out of approximately 138) come from Andras Bacsai, indicating he is the primary contributor driving most of the recent development efforts. His work spans across various aspects of the project including feature implementation, bug fixes, and refactoring.
Collaborative Efforts: There is a notable collaboration among team members, with multiple pull requests being merged that include contributions from various developers. This suggests a healthy collaborative environment where team members are actively contributing to shared goals.
Focus on Bug Fixes and Features: Recent activities show a balanced focus on both fixing existing issues (like unique constraints and deployment bugs) and adding new features (such as improved database handling and new templates). This dual focus is essential for maintaining software quality while also enhancing functionality.
Testing Emphasis: The introduction of tests alongside new features indicates a commitment to maintaining code quality and reliability through testing practices.
Diverse Contributions: While Andras leads in contributions, other team members also engage in meaningful ways, particularly in addressing specific issues or enhancing particular features. This diversity in contributions helps distribute knowledge across the team.
In summary, the development team is actively engaged in improving the Coolify project through significant contributions, collaboration, and a balanced approach to feature development and bug fixing.