TheFurya/nuzlocke-tracker
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update deployment beans to reflect SSH-based approach

Browse Source 
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>
This commit is contained in:
Julian Tabel
2026-02-10 09:45:58 +01:00
parent 83a17c8f15
commit 31355975e1
4 changed files with 23 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
.beans/nuzlocke-tracker-re0m--document-the-deployment-workflow.md
View File

@@ -5,7 +5,7 @@ status: in-progress
type: task
priority: normal
created_at: 2026-02-09T15:30:57Z
updated_at: 2026-02-09T16:55:02Z
updated_at: 2026-02-10T08:44:29Z
parent: nuzlocke-tracker-ahza
blocking:
- nuzlocke-tracker-aiw6
@@ -19,5 +19,7 @@ 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)
- 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/)