NDTR Apps

What This Is For

Use this as the NDTR admin runbook for directing Codex. NDTR runtime config, secrets, databases, groups, app registrations, and app data stay separate from MBI.

Default Instructions For Codex

Scope checks to the affected NDTR app or deploy wrapper.
Use shared family source code where practical, but keep NDTR runtime output under C:\MBI Apps\NDTR Apps.
Do not commit secrets; use NDTR Key Vault and NDTR app registrations.
For browser-visible problems, verify the served NDTR hostname and generated asset path.
Commit separately for portal/deploy wrapper changes and individual app-family changes.

NDTR Runtime Boundary

Portal runtime: C:\MBI Apps\NDTR Apps\Portal
App runtime roots: C:\MBI Apps\NDTR Apps\Nexus, Minesweeper, Org Chart, IT Inventory, and Scheduling
Logs: C:\MBI Apps\NDTR Apps\Logs
Secrets: ndtrappslivekv and ndtrappstestkv

Portal Publish

powershell.exe -NoProfile -File "C:\MBI Apps\NDTR Apps\Deploy\ndtr-publish-portal.ps1" -Environment All

This regenerates the NDTR-only portal output from the shared Apps Portal source and writes NDTR app metadata, NDTR auth config, and an NDTR-only change log.

Promotion Checks

Confirm the hostname is the NDTR live or test hostname.
Confirm sign-in redirects to the NDTR tenant.
Confirm app tiles use NDTR groups and NDTR URLs.
Confirm API health routes answer from the NDTR service instance.

Commit Boundary Rule

Keep NDTR deploy wrapper changes in the NDTR Apps repo.
Keep shared app-family code fixes in the app family repo.
Do not sweep unrelated repo dirt into a commit.

Apps

User

Your apps

Admin Tools