The frappe/frappe_docker project, which provides Docker images for deploying the Frappe framework and ERPNext, is facing significant challenges with architecture-specific compatibility, particularly with Apple Silicon.
Recent activity in the repository centers around resolving issues related to Docker compatibility, custom app integration, and environment configuration. Notably, issue #1458 highlights a critical problem with deploying on Apple Silicon due to manifest mismatches. This underscores a recurring theme of architecture-specific deployment challenges that need addressing. Additionally, issues like #1454 and #1433 point to difficulties users face with app dependencies and configurations when building custom images, indicating a potential need for clearer documentation or tooling improvements.
Recent issues and pull requests reveal a focus on addressing deployment challenges and enhancing configuration flexibility. The most pressing issue is #1458, which deals with Apple Silicon compatibility and remains open with high priority. Other issues, such as #1455 regarding unused cert-data volumes, suggest ongoing efforts to optimize resource management.
github-actions
SagarIdeen
dependabot[bot]
github-actions[bot]
lucca-rodrigues
The development team relies heavily on automation for maintaining infrastructure and dependencies, with minimal direct human intervention in feature development or bug fixes.
| Timespan | Opened | Closed | Comments | Labeled | Milestones |
|---|---|---|---|---|---|
| 7 Days | 1 | 0 | 0 | 0 | 1 |
| 30 Days | 6 | 3 | 4 | 0 | 1 |
| 90 Days | 23 | 21 | 35 | 0 | 1 |
| 1 Year | 106 | 92 | 253 | 4 | 1 |
| All Time | 633 | 614 | - | - | - |
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 |
|---|---|---|---|---|---|---|
| github-actions |  |
1 | 0/0/0 | 10 | 2 | 180 |
| dependabot[bot] |  |
1 | 3/3/1 | 3 | 3 | 18 |
| github-actions[bot] |  |
1 | 0/1/0 | 1 | 1 | 4 |
| Sagar |  |
1 | 0/1/0 | 1 | 1 | 3 |
| Lucca Rodrigues (lucca-rodrigues) | 0 | 1/0/1 | 0 | 0 | 0 |
PRs: created by that dev and opened/merged/closed-unmerged during the period
Recent activity in the frappe/frappe_docker repository indicates a focus on resolving issues related to Docker compatibility, custom app integration, and environment configuration. Notably, there are several issues concerning compatibility with Apple Silicon (ARM architecture), as seen in #1458, where users face challenges spinning up Docker containers due to manifest mismatches. This highlights a recurring theme of architecture-specific deployment challenges.
Another significant theme is the management and configuration of custom apps within the Docker setup, as evidenced by issues like #1454 and #1433. Users often encounter difficulties with app dependencies and configuration when building custom images, suggesting a need for clearer documentation or tooling improvements in this area.
Issues such as #1455 and #1456 reflect ongoing concerns about WebSocket and socket.io configurations, which are crucial for real-time updates in ERPNext. These issues point to potential gaps in documentation or default configurations that could be improved to enhance user experience.
The repository also shows a pattern of questions and requests for enhancements related to Docker Compose configurations, as seen in #1365 and #1369. These indicate a community interest in optimizing deployment processes and ensuring compatibility across different environments.
Overall, the activity suggests an active engagement with the community to address deployment challenges, particularly those related to architecture compatibility and custom app integration.
#1458: Unable to spin up Docker containers on Apple Silicon: No matching manifest for ARM in the manifest
#1455: Unused cert-data volume
#1458: Unable to spin up Docker containers on Apple Silicon: No matching manifest for ARM in the manifest
#1455: Unused cert-data volume
These issues highlight ongoing efforts to improve compatibility and resource management within the Docker setup for Frappe/ERPNext.
The frappe/frappe_docker repository is actively maintained, with a significant number of pull requests (PRs) reflecting ongoing development and community engagement. The repository focuses on providing Docker images for deploying the Frappe framework and ERPNext applications, supporting both development and production environments.
Summary
Quantified Reports
Detailed Reportsdocker/bake-action from 5.6.1 to 5.7.0, enhancing build summary support.HTTP_PUBLISH_PORT to example.env for customizable port settings.docker/bake-action from 5.5.0 to 5.6.1, improving GitHub annotations.docker-compose command.docker/bake-action from 5.5.0 to 5.6.0, superseded by #1453.pytest from 8.3.1 to 8.3.2, addressing bug fixes.docker/bake-action from 5.4.0 to 5.5.0, fixing toolkit issues.example.env.pytest from 8.2.2 to 8.3.1, introducing new features and improvements.The pull requests in the frappe/frappe_docker repository reveal several key themes and trends:
A significant portion of the PRs involves updating dependencies such as docker/bake-action and pytest. This indicates a proactive approach to maintaining the project's dependencies, ensuring compatibility with the latest versions and leveraging new features or security improvements.
Several PRs focus on enhancing documentation, such as updating commands or clarifying configuration options in files like README.md and example.env. This highlights an emphasis on user experience and accessibility, making it easier for both new and existing users to understand and use the repository effectively.
The repository shows active community involvement, with multiple contributors proposing changes or enhancements, such as adding new environment variables or fixing documentation errors. The maintainers appear responsive, closing or merging PRs promptly, which fosters a collaborative development environment.
Some PRs were closed without merging due to being superseded by other updates or lacking activity (e.g., #1451). This suggests that while there is active engagement, some contributions may not align with the project's direction or priorities at the time.
Updates to CI-related files (e.g., .github/workflows) indicate ongoing efforts to streamline automated processes like testing and building Docker images, which are crucial for maintaining a robust development pipeline.
Overall, the pull request activity reflects a well-maintained project with a strong focus on keeping dependencies up-to-date, improving documentation, and encouraging community participation while managing contributions efficiently through clear guidelines and prompt responses from maintainers.
github-actions
SagarIdeen
dependabot[bot]
github-actions[bot]
lucca-rodrigues
Automation and Dependency Updates: A significant portion of the recent activity is automated updates by bots (github-actions and dependabot[bot]), focusing on updating environment files and dependencies like docker/bake-action and pytest.
Minimal Human Contributions: Human contributors like SagarIdeen have made minimal changes, primarily focused on configuration updates (e.g., adding HTTP_PUBLISH_PORT variable).
Collaborative Efforts: Most collaborative efforts are seen in the form of automated pull requests managed by bots, indicating a reliance on automation for maintaining the repository.
Ongoing Maintenance: The repository shows signs of active maintenance with regular updates to environment configurations and dependency versions, ensuring compatibility and up-to-date functionality.
Overall, the recent activities suggest a focus on maintaining the infrastructure and dependencies of the frappe/frappe_docker repository through automated processes, with limited direct human intervention in terms of feature development or bug fixes.