e2a226e8b0
Two faults the guides plugin shipped with, both caught by gates that were already there. deploy/site-profile-universal.json never listed `guides`. That file is the profile the released Windows installer is built from, so the wizard would not have offered Guides at all - and worse, `flask plugin prune-schema` drops the tables of any plugin absent from the profile at provisioning (ADR-014). A site installing the next release would have had its guides table dropped. plugins/guides/models/guide.py imported shopdb.core.models.base directly. Plugins reach core only through shopdb.api or shopdb.plugins.base (ADR-001), and shopdb.api already re-exports BaseModel, so this is the same symbol by the supported path. The suite was red on main because of these two; it passes again.
24 lines
950 B
JSON
24 lines
950 B
JSON
{
|
|
"site": "universal",
|
|
"plugins": [
|
|
"backups",
|
|
"computers",
|
|
"employees",
|
|
"geenforce",
|
|
"guides",
|
|
"knowledgebase",
|
|
"machines",
|
|
"measuringtools",
|
|
"network",
|
|
"notifications",
|
|
"printedparts",
|
|
"printers",
|
|
"slides",
|
|
"tools",
|
|
"usb",
|
|
"warranty"
|
|
],
|
|
"locked": [],
|
|
"_comment": "The profile the released Windows installer is built from. Every bundled plugin that carries a manifest, so ONE exe serves any site: the wizard offers all of them and the operator ticks what that site uses. Plugins left unticked are never installed, and 'flask plugin prune-schema' drops their tables at provisioning (ADR-014). 'applications' is deliberately absent - it is manifest-less core and always ships. Build with: deploy/windows/installer/build-installer.sh deploy/site-profile-universal.json <repo>. Use site-profile.example.json instead only when a site genuinely needs a lean build; see ADR-013."
|
|
}
|