Software Orchestrator
5769c1cd22
- Auto-Registration-Bug behoben (register_project/get_project_id/resolve_project Trennung) - 25 Tests gruen (Pytest) - block_compactor-Tool refactored (Option B: Soft-Check statt Hard-Block) - 4 Restbaustellen gefixt - DB-Schema: plugin_settings-Tabelle hinzugefuegt - 3 Schattenprojekte aus DB geloescht - Plan v3 + Refactor-Plan + Worklog dokumentiert
1.5 KiB
1.5 KiB
name, description, tags
| name | description | tags | ||
|---|---|---|---|---|
| deployment-basics | Deployment documentation, environment setup, runbook, and rollback basics. |
|
Deployment Basics
Purpose
Standardize deployment operations: environment documentation, runbook creation, rollback procedures.
When to Use
- Before any production deployment
- When setting up a new environment
- After a release for handoff
- When rollback is needed
Procedure: Environment Setup
- Document required variable names from safe sources only (
.env.example, docs, schemas, compose placeholders, Coolify redacted status). Do not read live.env, runtime env dumps, credential stores, shell history, or logs to discover secret values. - Document required system dependencies
- Document required network access (ports, domains)
- Create env.example file with placeholders
Procedure: Runbook
- Pre-deploy: verify env, run tests, backup current state
- Deploy: step-by-step commands with expected output
- Post-deploy: health check, optional public reachability test, bounded error-log review
- Rollback: revert steps, restore backup, verify
Procedure: Rollback
- Identify the last known good state
- Revert code (git checkout )
- Restore database (if schema changed)
- Verify health and public reachability tests; skip authenticated tests unless user-provided test account exists for this task
- Document rollback reason in worklog
See Also
- Tool:
deployment_runner(if available in plugin) - Help:
operations/runtime.md