Development Guide
This module provides guidance for developers working on the Event and Membership Management system. It covers development workflow, CI/CD pipelines, local development setup, and build automation.
Workflow and CI/CD
Understanding the development process and continuous integration:
-
Development Workflow - GitFlow branching model and release process
-
Claude Design ↔ Claude Code Workflow - How web-based Claude Design and WSL-based Claude Code interoperate: feature inventory, user-story template, session kickoff, design→code handoff, phase-tag discipline
-
GitHub Actions CI/CD - CI/CD pipeline architecture and configuration
-
Repository Rules - Branch protection rulesets and code owner configuration
Local Development
Setting up a local development environment for front-end and full-stack development:
-
Running Backend Services Locally - Docker Compose configurations for starting backend dependencies
-
GreenMail Email Server - Local email testing without external SMTP servers
Build Conventions
The shared conventions every EMS service follows for build + image + chart:
-
Maven POM Conventions - Parent POM, Maven profiles determining build variants, shared plugin set
-
Jib Docker Build - Container image build via Jib, base image, layering, extra directories
-
Helm Chart Structure - Per-service chart layout, values schema, templates, secrets
-
Docker Compose for Developers - Local dev stack: MySQL, GreenMail, and gateway-only dev for frontend developers
Build Automation
Automation workflows for building and publishing artifacts:
-
Manual Helm Chart Release - Triggering Helm chart builds via GitHub Actions
-
Docker Compose Version Sync - Automatic synchronization of Docker image versions
Related Documentation
-
Helm Chart Patterns - How our Helm charts are structured
-
ArgoCD Deployment - Deploying to Kubernetes via ArgoCD