Files

T

SluijsensandClaude Sonnet 5 274946dbff Adds SlpModularCms.Api.Slave for local master/slave dev testing (Unit 1)

Relocates ModuleOrchestrator, ServiceCollectionExtensions, and
ApiPrefixConvention from SlpModularCms.Api into SlpModularCms.Core.Hosting
so a new Master-less SlpModularCms.Api.Slave host project (ports 5285/7222)
can share the same bootstrap code without duplicating it. This lets a
developer run a master instance and a slave instance side by side locally
to test the master/slave connection, without touching the existing
master/slave protocol itself.

Relocates the two orchestrator/convention test files from
Modules.Identity.Tests to Core.Tests, dropping an incidental
ProjectReference to SlpModularCms.Api that existed only for those tests.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-07-04 02:07:35 +02:00

983 B

Raw Permalink Blame History

Unit of Work — Requirement Map — Local Dev Master/Slave Setup

No user stories exist for this feature (User Stories stage was skipped — pure developer tooling, no user-facing functionality). Functional and non-functional requirements from requirements.md are mapped directly to units instead.

Requirement	Unit
FR-1: Slave-only backend host project	Unit 1
FR-2: Distinct local run configuration per instance	Unit 1
FR-3: Frontend configurable against either instance	Unit 2
FR-4: Documentation for the local master/slave workflow	Unit 2
NFR-1: No logic duplication between host projects	Unit 1
NFR-2: Isolation (separate databases)	Unit 1
NFR-3: Local-only scope	Unit 1 + Unit 2 (both — neither touches production/CI)
NFR-4: Secrets hygiene	Unit 1 (backend appsettings.local.json) + Unit 2 (frontend .env.slave.local)

All requirements are covered by exactly one or both units — no orphaned requirements.

983 B Raw Permalink Blame History

Unit of Work — Requirement Map — Local Dev Master/Slave Setup

983 B

Raw Permalink Blame History