How tecurious/tecurious-infra works
The tree suggests a self-hosted infrastructure repository: Kubernetes-related manifests for cluster workloads sit alongside operational and conceptual documentation. The likely operator workflow is managing infrastructure and services while consulting the runbooks, but no README content or source excerpts were provided to verify deployment order, routing, or service calls. Nodes therefore reflect visible subsystems; no edges are asserted without relationship evidence.
Components 16
Cluster Foundation
- GitOps Bootstrap
infrastructure/bootstrap/root-app.yaml - Cluster Configuration
infrastructure/cluster - Argo CD Setup
infrastructure/cluster/k3s-argocd
Hosted Workloads
- App Onboarding
infrastructure/apps/apps-onboard - 9router
infrastructure/apps/9router - Cloudflared
infrastructure/apps/cloudflared - Dev Strom
infrastructure/apps/dev-strom - PostgreSQL
infrastructure/apps/postgres - Postgres MCP
infrastructure/apps/postgres-mcp
Knowledge Base
- Technical Concepts
knowledge-base/Concepts - Firewall Concepts
knowledge-base/Concepts/Firewall - MCP Concepts
knowledge-base/Concepts/MCP - Rclone Concepts
knowledge-base/Concepts/Rclone - Infrastructure Runbooks
knowledge-base/infraRunbook - Remote Desktop Guide
knowledge-base/infraRunbook/remote-desktop
Other components
- Operator