platform

1,574 Commits 1 Branch 28 Tags

2 Commits

Include renames

Author	SHA1	Message	Date
pastilhasandClaude Opus 5	0230e62a71	the platform stops explaining what Headscale is Correcting my own reasoning from the last commit. I left "Headscale's API", "the Headscale admin credential" and similar alone on the grounds that they name the thing the plugin drives, so renaming them would make the sentences false. True as far as it goes, and it misses the point: those sentences are in the PLATFORM. It has no business knowing what Headscale is at all. Correct language in the wrong repository is still a remnant. Ten of them, each replaced with the platform's own vocabulary rather than the plugin's domain: - `crypto.ts` and `secret-store.ts` listed "the Headscale admin credential" among what one key used to protect. It is "the tailnet's admin credential" — the purpose, which is a word this repository owns. - `catalogue.ts` and `availability.ts` explained `alsoServes` — a LIVE mechanism — entirely through a Headscale example that left the repository. Restated as the general shape, with one parenthesis saying which case produced it. - The photos types file explained another plugin's sidecar. - `App.tsx` cited `/headscale/:section` as the example of a route pair; that route does not exist. `/photos/:section` does. - `plugins/router.ts` pointed at `useCompanionLogStream`, a hook that lives in a plugin now. - `registry.ts` said in the present tense that `headscale` is `admin` — the permission is the plugin's and it declares its own, so a member-facing enrolment surface would be the PLUGIN's to add, not this file's. - `proxy.sh` cited `headscale/schema.ts` as a style reference. That file is not in this repository. - machine-setup said "Its Headscale app" — the app is the Offscale plugin. `machine-setup/lib/tailscale.sh` keeps all ten of its mentions: it exists to explain tailscale, headscale and offscale to somebody choosing between them, on a core install, before any plugin exists. That is machine setup's subject, not the plugin's domain leaking upward. What survives elsewhere is only dated history — "was here until 2026-08-15", "It was: music, vault, slskd, headscale, …" — plus the notes about the real `headscale_servers` orphan and the secret-store key removed yesterday. Those record that something called headscale used to be here, which is a different claim from explaining what it does. tsgo clean, frontend builds, 873 pass / 7 fail unchanged, setup scripts parse. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-16 11:33:28 +00:00
pastilhasandClaude Opus 5	11710f283a	wire the reverse proxy in as officer-setup 12 ~/npm-setup-draft/setup-npm.sh, adapted to the script's own helpers and placed last — it is the only step that needs Officer already running. It ignores --unattended, as asked. Every other question in this script has a defensible default; a domain name, a DNS provider and that provider's API credentials do not, and the step is opt-in besides. Its prompts read stdin directly instead of going through confirm()/ask_required(), and they are NAMED APART (proxy_confirm, proxy_ask) so nobody later consolidates them into the shared helpers and quietly makes --unattended agree to publishing a public hostname. The valve is a TTY check rather than the flag: with no terminal there is nobody to ask, so it skips and prints the manual instructions. A cron-driven install still works. Five fixes to the draft: - `${OFFICER_REPO}/scripts/store-npm-credential.ts` — OFFICER_REPO is a git URL, not a directory, so that path was https://…/platform.git/scripts/… and the -f test could never pass. The whole persist-to-platform branch was dead code falling through to the print. Dropped it: the comment beside it already argued that not storing this password is a legitimate outcome, since only a human logging into the admin UI needs it. - NOT re-runnable, despite saying so. claim_admin returned early on an already claimed instance without setting NPM_EMAIL/NPM_PASSWORD, and get_token dereferenced both under set -u. Second run died on an unbound variable. It now asks for the existing credentials. - $HOME/dockers → $OFFICER_ROOT/dockers, matching data-path.ts. And the network is SETUP_DOCKER_NETWORK (`services`), not a second bridge called `officerdev`. - dig → getent hosts. dnsutils is not installed by this platform, so the check was command-not-found on a fresh VPS — and an empty answer is indistinguishable from "not resolving yet", so it waited the full 30 minutes before failing. - python3 → jq for host-side JSON. jq is already in the core package list; the one remaining python3 runs INSIDE the NPM container to read its own credential template, which is the point of reading it from there. Failure is contained: every function warns and returns non-zero rather than exiting, so a proxy that does not come up leaves a finished Officer install behind. Retry with `--only Proxy`. Verified: bash -n, shellcheck -S warning clean, --list shows Proxy, all seven external commands present, and the jq filters checked against sample payloads including the multi-line DNS credential. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-14 12:56:40 +00:00

Author

SHA1

Message

Date

pastilhasandClaude Opus 5

0230e62a71

the platform stops explaining what Headscale is

Correcting my own reasoning from the last commit. I left "Headscale's API", "the
Headscale admin credential" and similar alone on the grounds that they name the
thing the plugin drives, so renaming them would make the sentences false. True as
far as it goes, and it misses the point: those sentences are in the PLATFORM. It
has no business knowing what Headscale is at all. Correct language in the wrong
repository is still a remnant.

Ten of them, each replaced with the platform's own vocabulary rather than the
plugin's domain:

- `crypto.ts` and `secret-store.ts` listed "the Headscale admin credential" among
  what one key used to protect. It is "the tailnet's admin credential" — the
  purpose, which is a word this repository owns.
- `catalogue.ts` and `availability.ts` explained `alsoServes` — a LIVE mechanism —
  entirely through a Headscale example that left the repository. Restated as the
  general shape, with one parenthesis saying which case produced it.
- The photos types file explained another plugin's sidecar.
- `App.tsx` cited `/headscale/:section` as the example of a route pair; that route
  does not exist. `/photos/:section` does.
- `plugins/router.ts` pointed at `useCompanionLogStream`, a hook that lives in a
  plugin now.
- `registry.ts` said in the present tense that `headscale` is `admin` — the
  permission is the plugin's and it declares its own, so a member-facing enrolment
  surface would be the PLUGIN's to add, not this file's.
- `proxy.sh` cited `headscale/schema.ts` as a style reference. That file is not in
  this repository.
- machine-setup said "Its Headscale app" — the app is the Offscale plugin.

`machine-setup/lib/tailscale.sh` keeps all ten of its mentions: it exists to
explain tailscale, headscale and offscale to somebody choosing between them, on a
core install, before any plugin exists. That is machine setup's subject, not the
plugin's domain leaking upward.

What survives elsewhere is only dated history — "was here until 2026-08-15", "It
was: music, vault, slskd, headscale, …" — plus the notes about the real
`headscale_servers` orphan and the secret-store key removed yesterday. Those record
that something called headscale used to be here, which is a different claim from
explaining what it does.

tsgo clean, frontend builds, 873 pass / 7 fail unchanged, setup scripts parse.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-08-16 11:33:28 +00:00

pastilhasandClaude Opus 5

11710f283a

wire the reverse proxy in as officer-setup 12

~/npm-setup-draft/setup-npm.sh, adapted to the script's own helpers and placed last
— it is the only step that needs Officer already running.

It ignores --unattended, as asked. Every other question in this script has a
defensible default; a domain name, a DNS provider and that provider's API
credentials do not, and the step is opt-in besides. Its prompts read stdin directly
instead of going through confirm()/ask_required(), and they are NAMED APART
(proxy_confirm, proxy_ask) so nobody later consolidates them into the shared helpers
and quietly makes --unattended agree to publishing a public hostname.

The valve is a TTY check rather than the flag: with no terminal there is nobody to
ask, so it skips and prints the manual instructions. A cron-driven install still
works.

Five fixes to the draft:

  - `${OFFICER_REPO}/scripts/store-npm-credential.ts` — OFFICER_REPO is a git URL,
    not a directory, so that path was https://…/platform.git/scripts/… and the -f
    test could never pass. The whole persist-to-platform branch was dead code
    falling through to the print. Dropped it: the comment beside it already argued
    that not storing this password is a legitimate outcome, since only a human
    logging into the admin UI needs it.
  - NOT re-runnable, despite saying so. claim_admin returned early on an already
    claimed instance without setting NPM_EMAIL/NPM_PASSWORD, and get_token
    dereferenced both under set -u. Second run died on an unbound variable. It now
    asks for the existing credentials.
  - $HOME/dockers → $OFFICER_ROOT/dockers, matching data-path.ts. And the network
    is SETUP_DOCKER_NETWORK (`services`), not a second bridge called `officerdev`.
  - dig → getent hosts. dnsutils is not installed by this platform, so the check was
    command-not-found on a fresh VPS — and an empty answer is indistinguishable from
    "not resolving yet", so it waited the full 30 minutes before failing.
  - python3 → jq for host-side JSON. jq is already in the core package list; the one
    remaining python3 runs INSIDE the NPM container to read its own credential
    template, which is the point of reading it from there.

Failure is contained: every function warns and returns non-zero rather than exiting,
so a proxy that does not come up leaves a finished Officer install behind. Retry
with `--only Proxy`.

Verified: bash -n, shellcheck -S warning clean, --list shows Proxy, all seven
external commands present, and the jq filters checked against sample payloads
including the multi-line DNS credential.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-08-14 12:56:40 +00:00