Deploy script builds and pushes images to Gitea registry, then triggers Portainer stack redeployment via API. Includes preflight checks for branch and uncommitted changes. Also renames prod DB volume to avoid conflicts with dev and changes frontend port to 9080. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
24 lines
732 B
Markdown
24 lines
732 B
Markdown
---
|
|
# nuzlocke-tracker-aiw6
|
|
title: Create deploy script
|
|
status: in-progress
|
|
type: task
|
|
priority: normal
|
|
created_at: 2026-02-09T15:30:48Z
|
|
updated_at: 2026-02-09T17:22:53Z
|
|
parent: nuzlocke-tracker-ahza
|
|
blocking:
|
|
- nuzlocke-tracker-izf6
|
|
- nuzlocke-tracker-vpn5
|
|
- nuzlocke-tracker-xmyh
|
|
- nuzlocke-tracker-jzqz
|
|
---
|
|
|
|
Create a `./deploy.sh` script for the dev machine that automates the full deployment flow.
|
|
|
|
- Ensure the script runs from `main` branch (or warns if not)
|
|
- Build Docker images for API and frontend
|
|
- Tag images for the local registry (e.g., `unraid:5000/nuzlocke-api:latest`)
|
|
- Push images to the local registry
|
|
- Trigger the Portainer webhook to redeploy the stack
|
|
- Print status/confirmation of each step |