feat: Add generic deploy-vps action #7
No reviewers
Labels
No labels
priority/P0
priority/P1
priority/P2
priority/P3
size/L
size/M
size/S
size/XL
size/XS
state/done
state/in-progress
state/in-review
state/needs-refinement
state/ready
type/bug
type/chore
type/feature
type/refactor
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
amtronics/platform-actions!7
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/deploy-vps"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Issue
Closes #6
Problem
Portfolio vendors its VPS deploy action, hardcoding its own app-env schema
(turnstile/mailtrap/contact) and container names. To standardize deploys across
apps it has to become app-agnostic and live here.
Solution
Extract
deploy-vpsinto the org, generalized:app-env(newlineKEY=VALUE, writtenverbatim into the host runtime env) so each app supplies its own runtime.
healthcheck-containers(space-separated) replacing hardcoded names.grafana-prom-*— the observability contract this repo owns.byte-for-byte unchanged; no app name remains.
After merge → tag v3
Please tag
v3on the merge commit — v3 = openbao-fetch + notify-telegram +deploy-vps. Portfolio's adoption PR pins
@v3and only merges once v3 exists.Review notes
uses:and inputs.app-env; healthcheck loop → input; SSH heredoc threads the new var).