backstage

docs/REFERENCE.md

@@ -965,6 +965,52 @@ ignore:
 - Check Gitea Actions tab for workflow run status and logs
 - Monitor Anthropic usage dashboard for token consumption
 
+### Backstage (Developer Portal)
+
+**Chart**: `backstage/backstage`
+**Version**: `2.6.3`
+**Namespace**: `backstage`
+**Helm Repo**: `https://backstage.github.io/charts`
+
+**Purpose**: Internal developer portal where teams register and broadcast themselves, their applications, APIs, and systems. Provides a unified catalog, templates, and documentation hub.
+
+**Configuration** (`infra/values/base/backstage-values.yaml`):
+- PostgreSQL subchart enabled for persistence (standalone, 2Gi)
+- Traefik ingress with `websecure` entrypoint
+- App title: "Forte Developer Portal"
+- Catalog rules: Component, System, API, Resource, Location, Template, Group, User, Domain
+
+**Catalog Registration**:
+Teams register services by adding a `catalog-info.yaml` to their repo root:
+```yaml
+apiVersion: backstage.io/v1alpha1
+kind: Component
+metadata:
+  name: my-service
+  description: My service description
+  annotations:
+    backstage.io/source-location: url:https://git.forteapps.net/Forte/my-service
+spec:
+  type: service
+  lifecycle: production
+  owner: team-name
+```
+
+Then add the location to `backstage-values.yaml` under `appConfig.catalog.locations`.
+
+**Per-cluster Configuration**:
+To set the ingress hostname, create a per-cluster overlay values file (e.g., `infra/values/upc-dev/backstage-values.yaml`) with:
+```yaml
+backstage:
+  appConfig:
+    app:
+      baseUrl: https://backstage.example.com
+    backend:
+      baseUrl: https://backstage.example.com
+ingress:
+  host: backstage.example.com
+```
+
 ### Keycloak Client Registrar
 
 **Type**: CronJob (deployed via Keycloak Helm chart `extraDeploy`)