The FullStackHero .NET 8 Starter Kit, a comprehensive boilerplate for ASP.NET Core and Blazor applications, continues to face challenges with Docker deployment as evidenced by multiple user-reported issues. The project aims to streamline development with a clean architecture and multi-tenancy support.
Recent issues primarily revolve around Docker-related problems, such as builds not completing (#997) and Docker Compose failures (#999, #998). These recurring themes suggest a need for improved documentation or troubleshooting resources. Additionally, users are actively engaging with inquiries about upcoming features and compatibility with databases like SQLite (#1001).
Timespan | Opened | Closed | Comments | Labeled | Milestones |
---|---|---|---|---|---|
7 Days | 7 | 11 | 11 | 6 | 1 |
30 Days | 25 | 45 | 47 | 23 | 1 |
90 Days | 42 | 70 | 72 | 33 | 2 |
1 Year | 66 | 78 | 96 | 56 | 2 |
All Time | 275 | 258 | - | - | - |
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 |
---|---|---|---|---|---|---|
Mukesh Murugan | 1 | 2/3/0 | 38 | 383 | 56230 | |
maxiar | 1 | 1/1/0 | 1 | 30 | 28965 | |
Maxime (wtmaxim) | 0 | 0/0/2 | 0 | 0 | 0 | |
None (erhan355) | 0 | 0/0/1 | 0 | 0 | 0 | |
None (1hossin6494) | 0 | 1/0/1 | 0 | 0 | 0 | |
Alex Wittwer (alexwittwer) | 0 | 0/0/1 | 0 | 0 | 0 | |
Vladimir (enrichmentt) | 0 | 1/1/0 | 0 | 0 | 0 |
PRs: created by that dev and opened/merged/closed-unmerged during the period
The recent activity on the FullStackHero .NET 8 Starter Kit repository indicates a steady flow of issues, with 17 open issues currently logged. Notably, many of these issues revolve around Docker-related problems, indicating potential challenges in containerization or deployment processes. Additionally, there are inquiries about upcoming features and clarifications on existing functionalities, suggesting that users are actively engaging with the project and seeking guidance.
Several issues highlight themes of integration and compatibility, particularly with Docker and various database systems. For instance, issues related to Docker builds not completing or failing to run properly have been raised multiple times. This could point to a need for improved documentation or troubleshooting resources for users attempting to deploy the application in different environments.
Issue #1001: SQL version
Issue #1000: Failure to display information in the Grafana section
Issue #999: Docker compose up fails...
Issue #998: docker compose up fails ...
Issue #997: Docker build do not finishes
Issue #997: Docker build do not finishes
Issue #1000: Failure to display information in the Grafana section
Issue #1001: SQL version
The predominant themes among the recent issues include:
Docker Challenges: Multiple users have reported difficulties related to Docker builds and configurations, suggesting a need for clearer documentation or troubleshooting guides specific to Docker usage.
Feature Requests and Inquiries: Users are actively seeking information about upcoming features, particularly concerning version releases and compatibility with various database systems like SQLite.
Integration Issues: Several issues indicate complications arising from integrating various components (e.g., Grafana, PostgreSQL) within the project architecture, which may require further attention from maintainers to ensure seamless functionality across different environments.
Overall, while there is significant engagement from users, the challenges they face highlight areas where additional support could enhance user experience and project adoption.
The dataset consists of 550 closed pull requests (PRs) from the fullstackhero/dotnet-starter-kit
repository, with a notable recent activity involving the addition of Terraform module support and updates to the release drafter configuration. The PRs reflect a diverse range of enhancements, bug fixes, and feature additions, showcasing ongoing development efforts in this .NET starter kit.
PR #1006: feature : terraform modules support
Closed 3 days ago by Mukesh Murugan. This PR introduces support for Terraform modules, significantly enhancing infrastructure management capabilities within the project. It includes numerous additions to Terraform configuration files.
PR #1005: chore : Update release-drafter.yml
Closed 3 days ago by Mukesh Murugan. This PR updates the release drafter configuration to improve categorization of releases, which is crucial for maintaining clarity in versioning and release notes.
PR #999: Create dotnet.yml
Closed 6 days ago without merging. This PR proposed a new CI/CD pipeline but was rejected due to redundancy with existing workflows.
PR #990: Complete Open Telemetric Framework, New Dashboards and docker fixes
Closed 13 days ago by Mukesh Murugan. This substantial PR enhances observability through OpenTelemetry integration, adding dashboards and improving Docker configurations.
PR #973: fix blazor warning
Closed 30 days ago by Mukesh Murugan. This PR addresses specific warnings in Blazor components, contributing to code quality and maintainability.
PR #963: [v2] added opentelemetry metrics
Closed 38 days ago by Mukesh Murugan. This PR adds OpenTelemetry metrics support, which is essential for monitoring application performance.
PR #957: [v2] Change rate limit to options and add security headers
Closed 55 days ago by Mukesh Murugan. This PR enhances security by modifying rate limiting strategies and adding security headers.
PR #956: [v2] added signalr
Not merged due to unresolved conflicts and feedback regarding architecture changes necessary for scalability.
PR #955: added health check endpoint
Closed 58 days ago by Mukesh Murugan. This PR introduces a health check endpoint, improving the application's reliability monitoring capabilities.
PR #952: added rate limiting by IP
Closed 58 days ago by Mukesh Murugan. This PR implements IP-based rate limiting, enhancing security against potential abuse.
The pull requests in the fullstackhero/dotnet-starter-kit
repository illustrate a robust development cycle characterized by active contributions focused on enhancing functionality, improving security, and addressing technical debt. A significant number of recent PRs have been merged quickly, indicating an efficient review process led primarily by Mukesh Murugan, who appears to be the main contributor driving many of these changes.
The most recent activity includes the addition of Terraform module support (#1006) and updates to the release drafter configuration (#1005). These changes reflect a strategic move towards better infrastructure management and clearer release processes, which are critical for maintaining a high-quality codebase as the project scales.
Several PRs focus on integrating observability features such as OpenTelemetry (#990 and #963), which are essential for modern applications that require detailed performance metrics and tracing capabilities. The introduction of health check endpoints (#955) also aligns with best practices in cloud-native application development, ensuring that services can be monitored effectively in production environments.
Security has been a recurring theme in recent contributions, with multiple PRs addressing vulnerabilities or enhancing security measures (#957, #952). The proactive approach to implementing rate limiting based on IP addresses demonstrates an awareness of potential threats and a commitment to safeguarding user data.
The dataset also highlights instances where community contributions have been encouraged or where contributors have provided feedback on each other's work (e.g., discussions around PR #956). However, there are notable instances of unresolved conflicts that have led to some PRs not being merged (e.g., #956). This indicates a need for better communication or clearer guidelines on resolving conflicts within collaborative efforts.
Older PRs that remain unmerged or have been closed without action (e.g., #923 and #919) suggest areas where technical debt may accumulate if not addressed promptly. These include proposed enhancements that could improve functionality but are stalled due to lack of attention or prioritization.
In conclusion, while the fullstackhero/dotnet-starter-kit
demonstrates strong ongoing development with significant contributions towards enhancing functionality and security, there is room for improvement in managing community contributions effectively and addressing technical debt proactively. As the project evolves, maintaining clear communication channels among contributors will be vital for sustaining momentum and ensuring that all enhancements align with project goals.
Feature Development:
Bug Fixes:
Updates:
Collaborations:
The development team is actively engaged in enhancing the FullStackHero .NET 8 Starter Kit. Mukesh Murugan leads the contributions with a strong focus on both feature development and bug resolution, while collaboration with other developers enriches the project's capabilities. The ongoing nature of development suggests a robust roadmap ahead for further enhancements and community involvement.