Architecture: How to implement online platform deployment infrastructure?
Documentation for Sessions
🏗️ Architecture: How to implement online platform deployment infrastructure?
Date: 2026-01-17
Time: 00:02:28 UTC
Session: editor2-49.11
Agent: backend
Confidence: 95%
Status: ✅ Documented
📋 Decision Context
Question:
How to implement online platform deployment infrastructure?
Task: Session 49.5: Online Platform Deployment Architecture
🎯 Decision Made
Chosen:
GitLab with GitProviderService abstraction, branch-based drafts, GitLab CI/CD for builds
Options Considered:
- Gitea self-hosted
- GitLab Premium
- GitHub with Actions
- MongoDB blob storage
💭 Reasoning
GitLab Premium provides unlimited licensed users, built-in CI/CD with 10k compute minutes, and Groups/Projects model maps naturally to tenants/universes. Abstraction layer allows future provider switching. Branch-based drafts enable proper version control workflow (main=production, draft/*=wip). MongoDB stores metadata while GitLab stores actual code, leveraging each system's strengths.
📁 Files Involved
apis/backend-api/src/app/git-provider/gitlab-provider.service.tsapis/backend-api/src/app/drafts/drafts.service.tsapis/backend-api/src/app/build-pipeline/build-pipeline.service.tsapis/backend-api/src/app/platform-code/platform-code.service.tslibs/libs-foundational/core-models/src/lib/interfaces/git-provider.interface.ts
🔗 Related
- Decision ID:
dev_1768608148440_6f9jjt5 - Session: 49
- Workspace: editor2
Auto-generated by MCP Smart Consolidation