31355975e1
Remove Portainer references, mark NPM and env management as completed, update epic checklist and decided approach. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
25 lines
948 B
Markdown
25 lines
948 B
Markdown
---
|
|
# nuzlocke-tracker-re0m
|
|
title: Document the deployment workflow
|
|
status: in-progress
|
|
type: task
|
|
priority: normal
|
|
created_at: 2026-02-09T15:30:57Z
|
|
updated_at: 2026-02-10T08:44:29Z
|
|
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 (SSH, docker compose logs, etc.)
|
|
- How to set up the production environment from scratch (registry auth, NPM, SSH access)
|
|
- Deploy script flow: build images (podman/docker) → push to Gitea registry → SCP compose file → generate .env if missing → pull and start containers via SSH
|
|
- Production files live at `/mnt/user/appdata/nuzlocke-tracker/` on Unraid (compose file, .env, data/) |