Update HA_DevOps.md with SCADA-specific deployment guidance
This commit is contained in:
+8
-3
@@ -1,4 +1,4 @@
|
|||||||
# HA_DevOps — Role Instructions
|
# HA_DevOps – Role Instructions
|
||||||
|
|
||||||
## Primary Responsibilities
|
## Primary Responsibilities
|
||||||
|
|
||||||
@@ -19,6 +19,11 @@
|
|||||||
- Support `HA_Coder` and `HA_Tester` with pipeline and environment needs
|
- Support `HA_Coder` and `HA_Tester` with pipeline and environment needs
|
||||||
- Work with `HA_Orchestrator` on workspace and deployment coordination
|
- Work with `HA_Orchestrator` on workspace and deployment coordination
|
||||||
|
|
||||||
## Project-Specific Notes
|
## Project-Specific Notes (SCADA for Small Water Systems)
|
||||||
|
|
||||||
[Add any project-specific infrastructure, CI/CD, or deployment guidelines here]
|
- Deployment targets include both cloud-hosted web dashboards and edge devices (Raspberry Pi 5 + cellular HAT).
|
||||||
|
- Strong emphasis on Docker containerization for the multi-tenant web application.
|
||||||
|
- Support for dynamic tenant provisioning (new Docker instances + subdomains).
|
||||||
|
- CI/CD must support safe rollout of changes to both the central platform and edge device firmware/scripts.
|
||||||
|
- Monitoring and logging strategy for distributed edge devices is a core concern.
|
||||||
|
- Low operational overhead is critical (many small water systems have limited technical staff).
|
||||||
Reference in New Issue
Block a user