Add deployment strategy child task beans
Split the deployment strategy epic into 11 individual task beans with blocking dependencies. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,23 @@
|
||||
---
|
||||
# nuzlocke-tracker-re0m
|
||||
title: Document the deployment workflow
|
||||
status: todo
|
||||
type: task
|
||||
priority: normal
|
||||
created_at: 2026-02-09T15:30:57Z
|
||||
updated_at: 2026-02-09T15:31:15Z
|
||||
parent: nuzlocke-tracker-ahza
|
||||
blocking:
|
||||
- nuzlocke-tracker-aiw6
|
||||
- nuzlocke-tracker-3lfw
|
||||
- nuzlocke-tracker-up0b
|
||||
- nuzlocke-tracker-48ds
|
||||
---
|
||||
|
||||
Write documentation covering the full deployment setup and workflows.
|
||||
|
||||
- How to deploy (run `./deploy.sh`)
|
||||
- How to redeploy after changes
|
||||
- How to rollback to a previous version
|
||||
- How to manage the production instance (Portainer UI, logs, etc.)
|
||||
- How to set up the production environment from scratch (registry, Portainer, NPM, secrets)
|
||||
Reference in New Issue
Block a user