This CMS platform implements a sophisticated microservices architecture with multiple backend services, comprehensive infrastructure management, and extensive learning components for educational content delivery.

. ├── README.md ├── Makefile # Build automation and tasks ├── backend/ │ ├── cms-sys/ # Core CMS Service (Go) │ ├── gateway/ # API Gateway Service (Spring Boot) │ └── lms-sys/ # Learning Management System (Go) ├── components-learning/ # Educational Components & Examples │ ├── certificate_signing/ # Digital Certificate Generation │ ├── docker/ # Docker Learning Examples │ ├── elastic-search/ # Search Implementation │ ├── mfa/ # Multi-Factor Authentication │ └── postgres/ # Database Examples ├── docker-compose.yml # Main Orchestration ├── infra/ # Infrastructure as Code │ ├── migration/ # Database Migrations │ ├── github/ # CI/CD Configuration │ ├── schema/ # Database Schemas │ └── terraform/ # Infrastructure Provisioning ├── keys/ # Cryptographic Keys ├── scripts/ # Automation Scripts └── vault-init.sh # Vault Initialization 

cms-sys/ ├── cmd/main.go # Application entry point ├── internal/ # Core business logic │ ├── handler/ # HTTP handlers │ ├── repository/ # Data access layer │ ├── routes/ # API route definitions │ ├── service/ # Business logic layer │ └── types/ # Data structures ├── pkg/utils/ # Shared utilities ├── Makefile # Build and development tasks └── test/ # Test suites 

gateway/ ├── src/main/java/com/content_management_system/gateway/ │ └── GatewayApplication.java # Spring Boot application ├── src/main/resources/ │ └── application.yml # Configuration ├── Makefile # Java build automation └── src/test/ # Integration tests 

lms-sys/ ├── cmd/main.go # LMS application entry ├── internal/ # LMS-specific logic │ ├── config/ # Configuration management │ ├── handler/ # LMS API handlers │ ├── model/ # Domain models │ ├── repository/ # Data persistence │ └── service/ # Business services ├── pkg/utils/ # LMS utilities └── Makefile # Build and development tasks 

🐘 PostgreSQL Advanced Features (postgres/)

• Schema Management: Multi-tenant architecture patterns
• Geometric Data: PostGIS spatial data handling
• Functions & Domains: Advanced SQL programming
• GORM Integration: Go ORM implementation

• Cross-platform build commands
• Development environment setup
• Testing and linting automation
• Docker image building

• RSA key pair management
• Encryption/decryption utilities
• Secure communication setup

• Deployment automation
• Environment setup scripts
• Maintenance and monitoring tools

• Multi-service local development
• Service dependency management
• Environment variable configuration

• Service Independence: Each service can be developed, deployed, and scaled independently
• Technology Diversity: Go 1.24 for performance-critical services, Java 17 for gateway complexity
• Data Isolation: Each service maintains its own database and data models

• Separation of Concerns: Clear boundaries between presentation, business, and data layers
• Dependency Inversion: Business logic independent of external frameworks
• Testability: Comprehensive testing at unit, integration, and system levels

• Reproducible Environments: Consistent deployment across development, staging, and production
• Version Control: Infrastructure changes tracked and reviewed
• Automation: Minimal manual intervention in deployment processes

• Authentication: Multi-factor authentication and JWT token management
• Authorization: Role-based access control across services
• Encryption: End-to-end encryption for sensitive data
• Certificate Management: Digital certificates for document authenticity

Follow these steps to contribute to the Multi-Tenant CMS project:

git clone https://github.com/one-project-one-month/multi-tenants-cms-golang.git cd multi-tenant-cms-doc-golang

# Create and switch to your feature branch git checkout -b ft-CM-<according-to-your-ticket> # Example: git checkout -b ft-CM-user-authentication

📝 Branch Naming Convention: Use ft-CM-<feature-description> format based on your assigned ticket

• Focus: Work only on your assigned ticket/feature
• Quality: Follow project coding standards
• Testing: Ensure your code is properly tested

# Review what files have been modified git status # Review the actual changes git diff

# Add specific file(s) git add <fileName> # Or add all changes (use with caution) git add . # Or add multiple specific files git add file1.go file2.go

git commit -m "feat: add user authentication middleware  - Implement JWT token validation - Add role-based access control - Include unit tests for auth handlers"

💡 Commit Message Format: Use conventional commits format:

• feat: for new features
• fix: for bug fixes
• docs: for documentation
• test: for adding tests
• refactor: for code refactoring

# Fetch latest changes from remote git fetch origin # Pull latest changes to avoid conflicts git pull origin ft-CM-<according-to-your-ticket>

# Push your feature branch to remote git push origin ft-CM-<according-to-your-ticket> # If it's your first push on this branch git push -u origin ft-CM-<according-to-your-ticket>

# View commit history git log --oneline # Undo last commit (keep changes) git reset --soft HEAD~1 # Stash current changes git stash # Apply stashed changes git stash pop # Check remote branches git branch -r 

1. Create Pull Request: Go to GitHub and create a PR from your feature branch
2. Code Review: Wait for team review and address feedback
3. Merge: Once approved, your changes will be merged to main branch
4. Cleanup: Delete your feature branch after successful merge