[Proposal] - Working Group - Unified DevOps Café (Previous proposed name Self-Hosting)

A complete software lifecycle platform tools spans from development to deployment, monitoring, and long-term maintenance.

It begins with Development Environment Setup, where local machines are configured with IDEs, debugging tools, hot reloading, and lightweight databases for rapid iteration. Environment management using .env files, config libraries, and version managers like nvm or venv ensures consistency. Containerization with Docker and Compose further standardizes setups, making transitions between local, staging, and production seamless.

The Production Environment Setup emphasizes performance, security, and reliability. Applications run with optimized configurations, real databases, and robust infrastructure. CI/CD pipelines powered by GitHub Actions, GitLab CI/CD, or Jenkins automate testing, linting, and deployment, supporting strategies like blue-green and rolling updates for minimal downtime.

Post-deployment, Monitoring & Observability becomes central. Performance metrics, logging, and tracing tools provide insights into system health, while automated alerts ensure rapid response. Scalability strategies allow systems to handle growth, and strong security practices protect against evolving threats. Finally, ongoing Maintenance—including patching, dependency updates, and operational improvements—ensures stability and resilience.

Together, these focus areas form a unified ecosystem that accelerates development, safeguards production, and sustains applications through continuous improvement.


Focus Areas

Development Environment Setup

  • Local machine setup where code is written and initially tested
  • Typically includes debugging tools, hot reloading, verbose logging
  • Database often uses local instances or lightweight alternatives

Production Environment Setup

  • Live system serving real users
  • Optimized for performance, security, and reliability
  • Monitoring and logging focused on performance metrics

Essential Development Tools

Code Editors & IDEs

  • Visual Studio Code, Zed, NeoVim, etc.
  • Remote coding support
  • Extensions for syntax highlighting, debugging, version control setup

Environment Management

  • Environment variables (.env files)
  • Configuration files (JSON, YAML, TOML)
  • Tools like dotenv, config libraries

Containerization

  • Apple Container (For MacOS - Tahoe users)
  • Docker for consistent environments
  • Docker Compose for multi-service applications
  • Container registries (Docker Hub, ECR, GCR, etc)

Virtual Environments

  • Python: venv, conda
  • Node.js: nvm for version management

CI/CD Pipeline Tools

Continuous Integration

  • GitHub Actions, GitLab CI/CD, Jenkins
  • Automated testing, building, and deployment
  • Code quality checks (linting, security scanning)

Deployment Strategies

  • Blue-green deployments (near-zero downtime)
  • Rolling deployments

Monitoring & Observability

  • Goes beyond simple uptime checks by providing a full picture of system behavior.
  • Logs, metrics, and distributed traces work together to answer: what happened, why it happened, and how to fix it.
  • Observability tools help identify anomalies, bottlenecks, and dependencies across services.

Application Performance Monitoring (APM)

  • Tracks health of applications—response times, error rates, database queries, and external service calls.

Logging & Metrics

  • Centralized logging and structured metrics collection.
  • Enables proactive troubleshooting and data-driven decision-making.

Scalability

  • Horizontal and vertical scaling strategies.
  • Tools: Kubernetes, Docker Swarm, load balancers.

Security

  • Secure coding practices and runtime defenses.
  • Includes secrets management, vulnerability scanning, access controls, encryption, and compliance monitoring.

Maintenance

  • Regular updates, dependency management, and patching.
  • Automated workflows reduce downtime during maintenance windows.
  • Documentation and version control ensure long-term sustainability.

Who Can Join?

  • Frappe Developers, Coders & Testers – Anyone already building or experimenting with Frappe applications.
  • DevOps & SecOps Engineers – Professionals managing deployment pipelines, infrastructure, security, and system reliability.
  • Database Engineers – Those working with database design, optimization, and scalability.
  • Students & Professionals – Anyone curious about open-source software engineering tools, eager to learn and contribute.
  • Partners & Independent Builders – Individuals or organizations looking to develop apps and publish them to the Marketplace.

How We Will Operate

  • Discord App – Popular among developer communities, supports voice and chat seamlessly, with GitHub/bot integrations. (Proposed / yet to be created)
  • Forum for Discussions & Updates – Major updates and structured discussions will take place on discuss.frappe.com.
  • Community Meetups – Virtual, starting monthly, with frequency adjusted based on needs.
  • Collaboration First – Community-first initiative, encouraging open participation, contribution, and shared ownership.

Looking forward to collaborating as community first.

:link: For more context: Restarting community collaboration with working groups – Updates from Frappeverse ’25

6 Likes

General tasks for maintenance of frappe/frappe_docker and frappe/helm:

  • frappe/frappe_docker and frappe/helm repos are fairly automated. Update bot creates PR that can be merged by new maintainers.
  • All Green PR can be reviewed by human and merged or closed. For new contributors, “Approve Run” on their PR and wait for them to be Green or Red.
  • On new release, CONTRIBUTING.md has maintenance section. Maintainer need to follow that.
  • Support frappe developers with creating images. e.g. crm image, hrms image, lms image etc.
  • Daily watch the badges to be green. If pipeline badge becomes red, we have effectively caught something that will be build issue in future.
7 Likes
  • Use Raven for real-time communication
  • Continue structured discussions, major decisions, and updates via the forum/discussion board
  • Monthly virtual/all-hands meetups to sync up on progress; frequency can be increased if the pace demands it
  • Shared ownership; everyone is welcome to propose topics, contribute with code, documentation, monitoring, etc.

Join channel now at Frappe Community Chat | Raven

1 Like

If anyone is interested to be maintainer of the repo do respond.

There are PRs and issues piling up regularly.

1 Like