702ae7eaea
- Fix relative paths for cross-directory links (../ops/, ../services/, etc.) - Remove _(planned)_ markers from services that actually exist - Remove confusing _(reference CONTRIBUTING.md)_ comments - All links now properly reference correct paths - Build still passes successfully Co-authored-by: blackboxprogramming <118287761+blackboxprogramming@users.noreply.github.com>
37 lines
944 B
Markdown
37 lines
944 B
Markdown
---
|
|
id: runbooks-deploy-operator
|
|
title: "Deploy Operator Service"
|
|
slug: /runbooks/deploy-operator
|
|
description: "Runbook for deploying the BlackRoad OS Operator service"
|
|
tags: ["runbooks", "deployment", "operator"]
|
|
status: planned
|
|
---
|
|
|
|
# Deploy Operator Service
|
|
|
|
> 📋 **Status:** This runbook is planned and will be developed.
|
|
|
|
Step-by-step procedures for deploying the BlackRoad OS Operator service.
|
|
|
|
## Planned Content
|
|
|
|
This runbook will include:
|
|
- Pre-deployment checklist
|
|
- Deployment steps for Railway
|
|
- Worker scaling considerations
|
|
- Queue migration procedures
|
|
- Health check validation
|
|
- Rollback procedures
|
|
|
|
## Current Deployment
|
|
|
|
Currently, Operator deployment is handled via:
|
|
- Railway automatic deployments from main branch
|
|
- Manual deployments via Railway dashboard
|
|
|
|
## See Also
|
|
|
|
- [Service: Operator](../services/service-operator.md)
|
|
- [Operator Runtime](../ops/OPERATOR_RUNTIME.md)
|
|
- [Incident Playbook](./incident-playbook.md)
|