[LOADED_DOCS: 1 files, no new loads]

Add Deployment & Hosting section to documentation

Added a new section detailing how the FruitBank nopCommerce server is deployed, its relationship with the FruitBank plugin, and clarified that deployment configuration is managed externally. Also documented the removal of the legacy Mango/FruitBank folder and where deployment context is now described. No other changes made.
This commit is contained in:
Loretta 2026-04-26 14:10:47 +02:00
parent ce631560dc
commit 3f21389bde
1 changed files with 8 additions and 0 deletions

View File

@ -107,6 +107,14 @@ The first response's `[LOADED_DOCS: ...]` prefix must reflect **3 files** (this
> For core framework rules see: `.github/copilot-instructions.md` (in AyCode.Core repo)
> External repos in `own-dep-repos` are fully accessible — read their source code, docs, and `.github/copilot-instructions.md` freely when you need type definitions, base classes, or context. Do not limit yourself to the current workspace.
## Deployment & Hosting
This `FruitBank` product is the **nopCommerce server source** for a runtime instance deployed for the FruitBank company (fruit & vegetable wholesaler). The runtime instance hosts the **FruitBank plugin** (`Nop.Plugin.Misc.AIPlugin`, see Rule 17) compiled from the parallel plugin source folder. The plugin is the main vehicle for FruitBank-specific business logic; this repo is the broader server / domain layer it integrates with.
Deployment configuration (appsettings.json, plugins.json, themes, uploaded assets, runtime state) is managed via deployment artifacts **external to this source repo** — not authored here. Edits in this repo are FruitBank-specific server-domain code (entities, services, controllers, hooks); deployment-time concerns belong outside.
A separate placeholder folder (`Mango/FruitBank/`) historically tracked the deployment-host metadata as its own inherit-style instruction file (LLMP-DEC-16, LLMP-DEC-19). That folder was confirmed unused and removed (LLMP-DEC-51); the deployment-context information that was meaningful at the workspace level lives here, where the source code that actually gets deployed resides.
## Shared Agent Skills
Skills defined in other repos. **Two reactive skills are pre-loaded at session start; three user-gated skills are lazy-loaded on demand** — see `## Session Setup` above for the load matrix: