Deployments & CI/CD
Relevant source files
The following files were used as context for generating this wiki page:
The deployment and CI/CD strategy for RDM Digital focuses on a multi-layered approach to transitioning from a development environment to a stable production state. The project utilizes a "Sovereign Fortress City" architectural philosophy, where deployments are treated as civilizational updates to an urban operating system. Currently, the system is estimated at 72% maturity toward full production readiness, with key infrastructure such as the frontend build pipeline and Supabase Edge Functions integration already stable.
Sources: README.md:126-146, src/components/rdm/territory.tsx:7-12
Deployment Infrastructure & Strategy
The deployment architecture is built upon a React 18 SPA frontend served via Vite and a serverless backend powered by Supabase Edge Functions (Deno). The project emphasizes a "DevOps civilizatorio" (Civilizational DevOps) approach, which includes handling constitutional amendments and temporal rollbacks as part of its operational cycle.
Core Deployment Components
- Frontend Build Pipeline: Utilizes
pnpmfor package management and Vite for bundling. The build process includes strict TypeScript type checking. - Edge Functions: Serverless logic is deployed as Deno-based functions, providing an operational backend for critical processes like GitHub synchronization and telemetry ingestion.
- Database Migrations: SQL migrations are versioned and managed within the
supabase/migrationsdirectory to ensure consistent schema evolution across environments.
Sources: package.json:7-13, README.md:58-75, src/components/rdm/tomos.tsx:81-85
Deployment Lifecycle Diagram
The following diagram illustrates the high-level flow from code development to production deployment within the RDM Digital ecosystem.
The diagram shows the parallel deployment of frontend assets, database migrations, and Edge Functions that constitute a full system update.
Sources: package.json:7-13, README.md:126-135, supabase/migrations/
Build & Preview Operations
The project defines standardized scripts for local development and production preparation.
| Script | Command | Purpose |
|---|---|---|
dev | vite --host 0.0.0.0 | Starts local development server accessible on the network. |
typecheck | tsc --noEmit | Validates TypeScript integrity without generating output files. |
build | tsc --noEmit && vite build | Combined command for type validation and production bundling. |
preview | vite preview --host 0.0.0.0 | Serves the production build locally for final verification. |
Sources: package.json:7-13
GitHub Synchronization & Repository Management
A critical component of the CI/CD and deployment strategy is the "Evolutionary Repository" system. This system actively analyzes the GitHub organization OsoPanda1 and normalizes data across federations. This is handled by a dedicated github-sync Edge Function that performs automated scanning and classification of the codebase.
The sequence shows how the repository page triggers a backend sync to ensure the platform's metadata reflects the current state of the "database federada" (GitHub).
Sources: src/pages/Repositorio.tsx:28-40, supabase/functions/github-sync/index.ts:25-50
Production Readiness Roadmap
To reach 100% production maturity, the project outlines specific deployment and operational requirements:
- Hardening: Implementation of exhaustive Row Level Security (RLS) and systematic rate limiting.
- Observability: Integration of unified logging, metrics, and tracing across all modules.
- Automated Testing: Implementation of end-to-end (E2E) regression and load testing with blocking quality thresholds.
- Deployment Automation: Formalization of the CI/CD pipeline including canary deployment strategies and validated rollback procedures.
Sources: README.md:148-154, src/components/rdm/tomos.tsx:103-107
Conclusion
The deployment and CI/CD infrastructure of RDM Digital is currently in a "stabilized build" phase, supporting active synchronization between source code and its live representation on the platform. While the core build pipeline and serverless integration are functional, the roadmap emphasizes a transition toward automated canary releases and comprehensive observability to ensure the resilience of the "Sovereign Fortress" architecture.