// Run ServiceRadar web-ng locally against the live Kubernetes `demo` CNPG database for dashboard, SRQL, services, and UI testing. Use when a task asks to test with live demo data, run local Phoenix against demo CNPG, validate dashboard authoring with Playwright, or avoid fragile kubectl port-forward database access.
Build, sign, and roll ServiceRadar changes into the Kubernetes `demo` namespace using locally built images and immutable `sha-...` tags. Use when the user asks to deploy, refresh, roll, patch, or test code in `demo` before a release. Covers changed-image detection, copying unchanged images forward, OpenBao cosign signing, Argo patching, and rollout verification. Do not use for release cuts, Docker Compose refreshes, or non-demo namespaces unless the user explicitly redirects you.
Refresh the Kubernetes `demo` namespace with a web-ng-only change using the ServiceRadar fast path. Use when the diff only touches `elixir/web-ng/**` and the user wants a faster local demo rollout without rebuilding the full image graph. Covers scope verification, copying unchanged images forward, rebuilding the production `serviceradar-web-ng` release locally, pushing with `crane`, signing with the OpenBao release key, patching Argo, and verifying the rollout. Do not use when non-web-ng services changed or when cutting a release.
Cut a ServiceRadar release and roll the Kubernetes `demo` namespace to the resulting published semver image tag through ArgoCD Image Updater. Use when the user asks to update `VERSION` and `CHANGELOG`, run `scripts/cut-release.sh`, push the release refs, wait for published release artifacts, and then refresh `demo` to that released version. Do not use for pre-release local testing with unpublished images; use `$demo-local-rollout` or `$demo-web-ng-fastpath` for that.
Run ServiceRadar `elixir/web-ng` locally against the Docker Compose CNPG database with copied mTLS certs and Docker secrets, then verify dashboard UI changes with Playwright. Use when iterating on web-ng, dashboard package, custom React dashboard, UAL WiFi map, SRQL topbar, or browser screenshot behavior without rebuilding the web-ng release image.
Run ServiceRadar web-ng locally against the Kubernetes demo namespace FieldSurvey data, including CNPG NodePort access, NATS Object Store artifact access, authenticated browser checks, and Playwright screenshots for dashboard and FieldSurvey review iteration.
Run ServiceRadar Elixir database tests against the Kubernetes CNPG instance in the `srql-fixtures` namespace. Use when local localhost PostgreSQL is unavailable, when tests need current branch migrations, or when a user asks to use the srql-fixtures database for DB-backed validation. Covers scratch database creation, TLS-required NodePort connections, migrations, focused test commands, cleanup, and secret hygiene.
| name | demo-cnpg-local-web-ng |
| description | Run ServiceRadar web-ng locally against the live Kubernetes `demo` CNPG database for dashboard, SRQL, services, and UI testing. Use when a task asks to test with live demo data, run local Phoenix against demo CNPG, validate dashboard authoring with Playwright, or avoid fragile kubectl port-forward database access. |
Use this skill when local elixir/web-ng must run against the live demo
namespace CNPG database instead of Docker Compose or srql-fixtures.
From the ServiceRadar repo root:
.agents/skills/demo-cnpg-local-web-ng/scripts/start-local-web-ng.sh
The script:
demo/serviceradar-db-credentials without printing the password;192.168.6.82:5432;cnpg-rw-internal-lb and cnpg-local-dev;mix phx.server in elixir/web-ng with small DB pools and long queue windows for WAN/LAN testing.To only verify the live DB route without starting Phoenix:
.agents/skills/demo-cnpg-local-web-ng/scripts/start-local-web-ng.sh --check
Then use $playwright-cli against http://localhost:4000.
Permanent GitOps-managed objects:
demo/cnpg-rw-internal-lb192.168.6.82:5432demo/cnpg-allow-oracle-test-postgresCurrent known-good fallback from 192.168.2.134:
10.0.2.11:32040 via demo/cnpg-rw-internal-lb10.0.2.11:30455 via demo/cnpg-local-devIf 192.168.6.82:5432 fails but the NodePort path works, treat it as a
routing/L2 issue, not a web-ng or CNPG issue.
Use the playwright-cli skill for screenshots and smoke tests:
playwright-cli open http://localhost:4000/dashboards
playwright-cli screenshot --filename=tmp/demo-cnpg-dashboard-library.png
For dashboard authoring matrix checks:
playwright-cli run-code --filename elixir/web-ng/test/playwright/dashboard_authoring_matrix.playwright.js
Keep screenshots under tmp/ or .playwright-cli/; do not commit them.
kubectl port-forward for web-ng testing against demo; port-forward is fragile under Phoenix startup connection churn.CNPG_HOST_OVERRIDE and CNPG_PORT_OVERRIDE only when explicitly testing a specific route.4000 is already occupied.