Files

cproudlock 534f179ee6 Make main the lean product a site receives

main was 16 days and 259 commits behind the line the product is actually built
on, at contract 0.30.0 against 0.35.0, with no per-PC credential code at all. It
was neither current nor curated - just stale. This brings it forward and, at the
same time, makes it mean something: main is what a receiving site installs, and
nothing else.

WHAT IT CARRIES. Twelve plugins - backups, computers, endpoints, guides,
knowledgebase, machines, network, notifications, printers, slides, tools,
warranty - plus applications, which is manifest-less core and always ships. The
only manifest dependency inside that set is endpoints on computers, and both are
in it, so the closure is self-contained.

WHAT IT DOES NOT. employees, geenforce, measuringtools, printedparts and usb
stay on the site line. So do the Windows installer tree, the VM rehearsal
helpers, the agent tooling config, one site's data loader, the internal audit
and findings records, and the planner spreadsheet. 1,135 tracked files against
1,438.

A REMOVAL THAT BREAKS THE APP IS NOT A REMOVAL, and two nearly shipped:

deploy/site-profile-universal.json still named all seventeen plugins. It is the
file docs/DEPLOY.md tells a site to provision from, so a fresh install would
have failed at `flask plugin apply-profile` with PluginError - the first thing a
receiving site does, broken by the branch meant to serve them. It now names the
twelve that exist, and its comment says the two must agree.

agent/ was never refreshed. Whoever populated this branch copied shopdb/,
plugins/, frontend/ and tests/ from the site line and left the agent tree at its
September state: 22 C# and PowerShell sources missing, including AgentCredentials,
EnrollmentService, AgentHttpFactory and the fleet-alert client, plus one file the
site line had deleted still present. The old tree is internally consistent, so it
compiles, and nothing in CI builds it - every gate was green over a server that
speaks enrollment and per-PC credentials to a bundled agent source that cannot.
Resynced whole.

DECISIONS THIS ENCODES, rather than defers:

- The plugin-authoring lab builds printedparts, whose manifest depends on
  employees, so it could not stay. The lab remains on the site line and main
  ships no build-along tutorial. That is a real loss for an adopting developer
  and is recorded here rather than discovered later.
- Recognition, Training and Recertification notifications are no longer seeded.
  Each splits one notification into a card per employee and renders a photo,
  which needs a plugin this branch does not bundle. Seeding them would offer an
  author a type that cannot resolve anybody. A site that installs employees gets
  them from that plugin's own seed.
- Windows/IIS is documented as the legacy path throughout, and the README leads
  with Docker, because that is what a receiving site gets.

The API description is regenerated for THIS branch - 347 paths and 483
operations, down from 415 and 573 - so the published contract describes what is
here rather than what the site line serves. docs/CONFIG.md lost the two
measuring-tool label keys the code no longer declares, which two lanes had
decided opposite ways.

Suite: 3124 passed, 6 skipped. Naming and style gates pass. The docs gates run
rather than skip, and every index line count is derived from the file it names.

2026-09-19 11:24:40 -04:00

2.2 KiB

Raw Blame History

ShopDB dev build - quick test

Two dev builds you can stand up on a Windows box with Docker Desktop. You run one PowerShell script: it checks your dependencies (offers to winget-install anything missing), then PULLS a prebuilt image from GHCR and starts the stack in Docker. Nothing is compiled on your machine - no Node, no npm, no source build - so it works on a box that has only Docker installed.

This is for LOOKING at a build, not changing one. To edit the code, you want a real dev environment: DEVELOPMENT-SETUP.

What you need

Windows with Docker Desktop running.
Git for Windows (winget install Git.Git).
A GitHub login for this private repo/registry already stored on the box. If you have cloned this repo before, or signed in to GitHub in Visual Studio or VS Code, you already have it - the script uses that stored credential automatically. If Docker cannot pull the image, sign in once with docker login ghcr.io (use a GitHub username and a personal access token that has read:packages), then re-run the launcher.

Get the launcher

You will be sent Start-ShopDBDev.ps1 directly. Save it anywhere (for example your Downloads folder) and open PowerShell in that folder.

Bleeding edge (main, the trunk)

powershell -ExecutionPolicy Bypass -File .\Start-ShopDBDev.ps1 -Channel edge

Comes up at https://localhost:5011. Red DEV badge in the sidebar. Pulls the edge image.

Stable (newest release tag)

powershell -ExecutionPolicy Bypass -File .\Start-ShopDBDev.ps1 -Channel stable

Comes up at https://localhost:5001. No DEV badge. Pulls the stable image.

Notes

Both stacks can run at the same time - they use different ports and separate Docker volumes, so they do not collide and each keeps its own database.
Each launch pulls the latest image for the channel, so re-running the launcher is how you pick up a new build.
First page load shows a self-signed cert warning (expected for a dev box).
Stop a stack: docker compose -p shopdb-stable down (or shopdb-edge).

2.2 KiB Raw Blame History