The README gave Windows/IIS and Docker equal billing, and led with the installer
under "Fast path (Docker)" - which reads as though the slower, more official
route is the .exe. That is backwards now: Docker is what a new site gets and
IIS is the legacy path, supported for the sites already on it.
Changed where a reader looks first: two lines under the title saying a site runs
containers, Distribution naming the installer as legacy, and the Docker section
retitled "Standing up a site" rather than a fast path. The venv instructions are
marked development-only, because they are for working on ShopDB rather than
running it.
Nothing about the IIS material was removed. It is what production runs today.
Clone-to-first-change onboarding, plus .vscode launch/tasks/extensions
so F5 debugs the backend and a task runs both dev servers. Fix the
README manual path to run the backend on 5001 (the frontend proxies
there; the default 5000 loaded nothing).
Flask + Vue rewrite of the classic-ASP shopdb, built as a plugin
framework so sister GE Aerospace sites can adopt it. Product version
0.7.0-pre-0.8.0, plugin contract 0.11.0, 966 backend tests.
Key entry points:
- docs/INSTALL-WINDOWS-IIS.md - tested Windows + IIS install runbook
(own-site and subpath deployment methods)
- docs/PILOT-DEPLOY.md - production pilot: stand up + import + verify
- docs/IMPORT-API.md - schema-agnostic legacy data import contract
- scripts/site_imports/wjf/ - West Jefferson reference import loader
- docs/adr/ - twelve accepted architecture decision records
