Infrastructure
Deployment topology, environment contracts, and operational assumptions for SterlingIndex.
This section documents the repo-visible deployment model for SterlingIndex:
- local backend and dependency orchestration through
infra/docker-compose.local.yml - dedicated VPS deployment assets under
infra/vps - production-oriented Kubernetes manifests under
infra/k8sas a secondary reference path - the hostname, environment-variable, and secret-management contract that connects
apps/www,apps/docs,apps/dashboard, the activeapps/admin-desktopElectron admin, optionalapps/legacy-admin, andservices/platform-api
The focus here is intentionally limited to infrastructure that is represented in the repository. Managed services or external SaaS configuration only appear when the repo already references them directly.