chore(deploy): gp.nano migration helper scripts and pre-flight checklist#23
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds the operator-facing scripts and pre-flight checklist that finalise the gp.nano migration prep started in #22. With this in, the only manual work left for the actual migration is provisioning the gp.nano VPS in the Cubepath panel and following the runbook.
scripts/migrate-to-nano/bootstrap-host.sh— idempotent SSH-time bootstrap for a fresh gp.nano host (Docker engine + compose plugin, 2 GB swap, Dokploy installer). Single curl-pipe-bash invocation.scripts/migrate-to-nano/verify-nano.sh— post-deploy smoke test (frontend 200, /health 200, chat 503, province forecast contains q50). Run against the Dokploy preview URL before DNS cutover, then again after.scripts/migrate-to-nano/env-vars-checklist.md— exact env vars to carry from the gp.starter Dokploy panel, classified by whether mismatch is data-destructive (FIELD_ENCRYPTION_KEY, VAPID keys), session-invalidating (JWT_SECRET, NEXTAUTH_SECRET), or low-risk.docs/deployment/nano.md— adds a "Pre-flight (24 h before cutover)" section, references the new scripts, and tightens the cutover steps to point at the verify script.Test plan