egg/DashBoard
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
b56e80381bc3e67a8289063c8c5db8530252486b
DashBoard/openspec/specs/conda-systemd-runtime-alignment/spec.md
beabigegg b56e80381b chore: reinitialize project with vite architecture
2026-02-08 08:30:48 +08:00

1.4 KiB
Raw Blame History

conda-systemd-runtime-alignment Specification

Purpose

TBD - created by archiving change stability-and-frontend-compute-shift. Update Purpose after archive.

Requirements

Requirement: Production Service Runtime SHALL Use Conda-Aligned Execution Paths

Service units and operational scripts MUST run with a consistent conda-managed Python runtime.

Scenario: Service unit starts application

  • WHEN systemd starts the dashboard service and watchdog
  • THEN both processes MUST execute using the configured conda environment binaries and paths

Requirement: Watchdog and Runtime Paths MUST Be Operationally Consistent

PID files, restart flag paths, state files, and worker control interfaces SHALL be consistent across scripts, environment variables, and systemd units.

Scenario: Watchdog handles restart flag

  • WHEN a restart flag is written by admin control endpoints
  • THEN watchdog MUST read the same configured path set and signal the correct Gunicorn master process

Requirement: Deployment Documentation MUST Match Runtime Contract

Runbooks and deployment documentation MUST describe the same conda/systemd/watchdog contract used by the deployed system.

Scenario: Operator follows deployment runbook

  • WHEN an operator performs deploy, health check, and rollback from documentation
  • THEN documented commands and paths MUST work without requiring venv-specific assumptions