NaNs: first session on the new host — hostname + user rename, profile re-point, deployment facts #72

Open
opened 2026-10-30 01:22:35 +00:00 by dsh · 0 comments
Owner

State

Operator: a new small server (8 GiB RAM) becomes the DSH host tomorrow. On that box:

  • hostname changes (the DSH web URL and its trusted-host/tailnet entries move);
  • the user is renamed dsh → deeps, and the DSH home migrates with it (~/.dsh/profiles/web, credentials, sessions);
  • Forgejo stays on the old server (git.pvlb.dev does not move), so gitea_* URLs and the token keep working;
  • the plugin stays a 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:link bootstrap, HMR root, common failures.
  • GIT.md — gitignored; copy it from pvlb-dev on the new host if identity/signing is missing.

Checklist

  1. node scripts/dev-link-dsh.mjs in this checkout (a link: install needs the peers).
  2. Confirm the profile row still points at the checkout (plugin_manager action=list_bundles), toggle the bundle off/on, hard-refresh the GUI.
  3. gitea_whoami through the dispatcher surface plus one gitea_issue_list to prove credential and baseUrl survived the migration.
  4. npm run check (expect 240 tests, leak scan clean).
  5. Update devops/state.md: new hostname, GUI/trusted-host URL, $DSH_PROFILE_DIR, the pnpm path (the /opt/node-v24… layout may differ), RAM, and the "facts checked" date. devops/deploy.md gets the same treatment if any command changed.
  6. Re-wrap the last two sessions' LOGS entries here; do not tag anything for the migration (the plugin code did not change; v0.8.9 already carries the release).

Acceptance

  • npm run check green on the new host, plugin loaded with the two-tool dispatcher default.
  • devops/state.md describes the new box, not the old one, and no command in devops/deploy.md references the vanished dsh home or the old hostname.
  • The first gitea_* call from the new host succeeds against the unchanged Forgejo.

Bundle

Nothing scheduled for 0.9.0 yet (history compaction only) — keep this issue limited to the migration so it closes in that first session.

## State Operator: a new small server (8 GiB RAM) becomes the DSH host tomorrow. On that box: - **hostname changes** (the DSH web URL and its trusted-host/tailnet entries move); - the **user is renamed `dsh` → `deeps`**, and the DSH home migrates with it (`~/.dsh/profiles/web`, credentials, sessions); - **Forgejo stays on the old server** (`git.pvlb.dev` does not move), so `gitea_*` URLs and the token keep working; - the plugin stays a `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`](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`](devops/deploy.md) — install/reload loop, `dev:link` bootstrap, HMR root, common failures. - [`GIT.md`](GIT.md) — gitignored; copy it from `pvlb-dev` on the new host if identity/signing is missing. ## Checklist 1. `node scripts/dev-link-dsh.mjs` in this checkout (a `link:` install needs the peers). 2. Confirm the profile row still points at the checkout (`plugin_manager action=list_bundles`), toggle the bundle off/on, hard-refresh the GUI. 3. `gitea_whoami` through the dispatcher surface plus one `gitea_issue_list` to prove credential and baseUrl survived the migration. 4. `npm run check` (expect **240 tests**, leak scan clean). 5. Update `devops/state.md`: new hostname, GUI/trusted-host URL, `$DSH_PROFILE_DIR`, the `pnpm` path (the `/opt/node-v24…` layout may differ), RAM, and the "facts checked" date. `devops/deploy.md` gets the same treatment if any command changed. 6. Re-wrap the last two sessions' LOGS entries here; **do not tag** anything for the migration (the plugin code did not change; `v0.8.9` already carries the release). ## Acceptance - `npm run check` green on the new host, plugin loaded with the two-tool `dispatcher` default. - `devops/state.md` describes the new box, not the old one, and no command in `devops/deploy.md` references the vanished `dsh` home or the old hostname. - The first `gitea_*` call from the new host succeeds against the unchanged Forgejo. ## Bundle Nothing scheduled for `0.9.0` yet (history compaction only) — keep this issue limited to the migration so it closes in that first session.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
dsh-plugins/dsh-gitea#72
No description provided.