Files
ScadaBridge/docs/api-specs/README.md
T
Joseph Doherty 48517b49fb docs: relabel wonder-app-vd03 as DEV, not production, across plans, records, reviews and API specs
vd03 is the DEV box (vd = DEV, vq03/vq04 = QA). Historical docs called it prod/production.
Only vd03-referential uses are changed; generic 'production' wording (production HOCON,
production code paths, ASPNETCORE_ENVIRONMENT=Production, real-world production guidance)
is unchanged. One verbatim git commit message quoted in PLAN-07 is left as recorded.
2026-11-10 15:11:45 -05:00

10 lines
681 B
Markdown

# API Specs (as deployed)
Point-in-time captures of ScadaBridge's **own** externally-called contracts — Inbound API methods and
the site-side handshakes behind them — pulled from a live environment's management API. Method
definitions are config-as-data in the central ConfigDb (not source-controlled), so these files are the
durable record; each states which environment it was captured from and when. Legacy/predecessor
system specs live in [`../former-api-specs/`](../former-api-specs).
- [`Delmia-Recipe-Download-API.md`](Delmia-Recipe-Download-API.md) — `POST /api/DelmiaRecipeDownload` (DELMIA Apriso recipe-download notification), DEV `wonder-app-vd03`, 2026-09-02.