Infrastructure and Orchestration Services
Entry point to the knowledge base and technical guides for the deployment and maintenance of services in Portelcore.
Welcome to the Infrastructure Services section. This documentary compendium serves as the operations manual and technical standards for the provisioning, securing, and maintenance of support, orchestration, and automation systems in Portelcore.
🗺️ Services Navigation Map
Sección titulada «🗺️ Mapa de Navegación de Servicios»To facilitate technical consultation, the documentation is organized into four large operational areas:
Tactical guides and commands for agile container engine administration.
- Content: Storage cleanup, exclusion of protected images, and Docker garbage collection automation.
Architecture manual for the secure deployment of automated workflows and processes.
- Content: Persistence on PostgreSQL, network isolation via Docker Bridge, and secure routing via Cloudflare Tunnels (Zero Trust).
🚀 Plane.so (Commercial Project Management)
Sección titulada «🚀 Plane.so (Gestión de Proyectos Commercial)»End-to-end deployment of the Plane project control platform in its Prime version.
- Content: Management via
prime-cli, strict SSL configuration with Cloudflare Origin certificates, port optimization, and Reverse Proxy with Nginx.
🎯 Redmine on Proxmox (Task and Incident Management)
Sección titulada «🎯 Redmine en Proxmox (Gestión de Tareas e Incidencias)»Infrastructure as Code (IaC) for the deployment of Redmine on secure virtualization in Proxmox.
- Content: Ubuntu Server preparation, multi-container composition (Redmine + MySQL), dedicated SMTP configuration, and backup directives (Day-2 Operations).
📊 Service Orchestration Architecture
Sección titulada «📊 Arquitectura de Orquestación de Servicios»The following diagram represents how external user requests are securely routed and isolated to each of the microservices and platforms hosted on Portelcore's local network:
graph TD User([🌍 Usuario / Internet]) -->|Tráfico Cifrado HTTPS| CFTunnel["🛡️ Cloudflare Tunnel<br>(Zero Trust Edge)"] CFTunnel -->|Túnel Seguro a Host Local| RevProxy["🚀 Proxy Inverso Nginx / Traefik"]
subgraph "Docker Host (Red Bridge Aislada)" RevProxy -->|Puerto 5678| n8n["🤖 Automatización n8n<br>(PostgreSQL Backend)"] RevProxy -->|Puerto 8080| Plane["🚀 Plane.so PM Tool<br>(Prime Edition)"] RevProxy -->|Puerto 3000| Redmine["🎯 Redmine Incidencias<br>(Ruby/MySQL VM)"] RevProxy -->|Comando Pruning| Docker["🐳 Docker Engine<br>(Gestor de Recursos)"] end
classDef edge fill:#f38020,stroke:#d96814,color:#fff;
class CFTunnel edge;🛠️ Operation and Quality Standard
Sección titulada «🛠️ Estándar de Operación y Calidad»All services implemented under the Portelcore infrastructure must comply with the following design directives:
- ✓ Perimeter Security: Direct exposure of database management ports or internal services to the internet is prohibited. All public traffic must pass through secure tunnels or encrypted reverse proxies.
- ✓ Data Persistence: All persistent storage volumes must be mounted on backed-up local logical volumes or compatible cloud storage solutions.
- ✓ Declarative Infrastructure: All deployments must be orchestrated using
docker-compose.ymlfiles and.envenvironment variable files versioned in Git (excluding actual secrets).

