🏗️ Architecture: Where should generated platform code be stored for online us...

Date: 2026-01-16
Time: 23:12:53 UTC
Session: editor2-49.5
Agent: architecture
Confidence: 90%
Status: ✅ Documented

📋 Decision Context

Question:

Where should generated platform code be stored for online users?

Task: Design online platform generation architecture for non-local users

🎯 Decision Made

Chosen:

Self-hosted Gitea with abstraction layer for future GitLab migration

Options Considered:

1. MongoDB with GridFS
2. S3/Cloud blob storage
3. GitHub repos per user
4. GitLab self-hosted
5. Gitea self-hosted

💭 Reasoning

1. MongoDB is for configuration/metadata, not source code (16MB limit, no versioning). 2. S3 lacks branching semantics needed for drafts system. 3. GitHub has rate limits and external dependency. 4. GitLab is overkill (2GB+ RAM) for current needs. 5. Gitea is lightweight (~256MB), self-hosted, has organizations for multi-tenant mapping, native branching for drafts, and webhooks for build pipeline. 6. Abstraction layer (GitProviderService interface) allows easy migration to GitLab if needed later.

📁 Files Involved

• apis/backend-api/src/app/git-provider/
• docs/english/sessions/editor2/session-49/49.4-online-platform-generation-architecture.md

🔗 Related

• Decision ID: dev_1768605173511_ldvat6l
• Session: 49
• Workspace: editor2

Auto-generated by MCP Smart Consolidation