NaNs: first session on the new host — hostname + user rename, profile re-point, deployment facts #72
Labels
No labels
NaNs
area/dsh
area/forgejo
experiment
priority/later
priority/next
priority/now
type/bug
type/task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
dsh-plugins/dsh-gitea#72
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
State
Operator: a new small server (8 GiB RAM) becomes the DSH host tomorrow. On that box:
dsh→deeps, and the DSH home migrates with it (~/.dsh/profiles/web, credentials, sessions);git.pvlb.devdoes not move), sogitea_*URLs and the token keep working;link:install of this checkout.Next step
In the first session on the new host: re-bootstrap this checkout, re-point the profile at it, and update the deployment facts.
Read first
devops/state.md— the deployment facts (hostname, profile paths, pnpm path, GUI URL) describe the old box and go stale the moment the home moves.devops/deploy.md— install/reload loop,dev:linkbootstrap, HMR root, common failures.GIT.md— gitignored; copy it frompvlb-devon the new host if identity/signing is missing.Checklist
node scripts/dev-link-dsh.mjsin this checkout (alink:install needs the peers).plugin_manager action=list_bundles), toggle the bundle off/on, hard-refresh the GUI.gitea_whoamithrough the dispatcher surface plus onegitea_issue_listto prove credential and baseUrl survived the migration.npm run check(expect 240 tests, leak scan clean).devops/state.md: new hostname, GUI/trusted-host URL,$DSH_PROFILE_DIR, thepnpmpath (the/opt/node-v24…layout may differ), RAM, and the "facts checked" date.devops/deploy.mdgets the same treatment if any command changed.v0.8.9already carries the release).Acceptance
npm run checkgreen on the new host, plugin loaded with the two-tooldispatcherdefault.devops/state.mddescribes the new box, not the old one, and no command indevops/deploy.mdreferences the vanisheddshhome or the old hostname.gitea_*call from the new host succeeds against the unchanged Forgejo.Bundle
Nothing scheduled for
0.9.0yet (history compaction only) — keep this issue limited to the migration so it closes in that first session.