LMS Startup
Summary
Startup registers dependencies, optionally applies migrations and development seed behavior, then maps health, service information, and Training endpoints.
Reference Content
| Stage | Verified behavior |
|---|---|
| Composition | Observability, messaging, tenant context, database, outbox store, Document client, endpoint discovery, and health are registered |
| Development behavior | Migration and seed logic is conditionally invoked by source |
| Middleware | Correlation and exception translation are applied |
| Routes | Health, service information, and Training API groups are mapped |
| Missing evidence | No Training hosted relay registration; no production startup runbook or readiness gate |
Operators should validate approved environment configuration and health through organization-owned processes. This page intentionally provides no startup command.
Safety and confirmation boundary
No production command, secret, configuration value, internal address, infrastructure detail, direct data change, or replay instruction is provided. Production ownership, approvals, service objectives, alerting, and recovery authority require confirmation.
Source References
microservices/src/training-service/Program.csmicroservices/src/training-service/Infrastructure/DevelopmentSeeder.csmicroservices/src/training-service/Dockerfile
Related Articles
See Also
Keywords
- LMS operations
- LMS Startup
Revision Information
- Status: Draft
- Last reviewed: 2026-07-17
- Review cycle: Quarterly