wild-pc

wild-cloud/wild-pc

Fork 0

Commit Graph

Author	SHA1	Message	Date
Paul Payne	05b28cb584	Rename Castle -> Wild PC across the repo Repo-side rename only (Phases 1-3 of the migration plan); the live box (~/.castle, systemd units, /data/castle, domains) is a separate cutover. - Slug `castle` -> `wildpc`: CLI command, module names (wildpc_core/cli/api), dist names, entry point `wildpc = wildpc_cli.main:main`. - Identifiers: CastleConfig/NATSClient/DirError/MDNS -> Wildpc. - Env/constants: CASTLE_ -> WILDPC_*; ~/.castle -> ~/.wildpc, castle.yaml -> wildpc.yaml, /data/castle -> /data/wildpc. - Systemd UNIT_PREFIX castle- -> wildpc-; own programs castle-api/gateway/etc. - Display prose "Castle" -> "Wild PC" in docs, agent-guide files, README, frontend. - Package dirs and bootstrap yaml renamed via git mv; lockfiles regenerated; redundant nested uv.lock files dropped (workspace root lock is authoritative). Tests: core 273, cli 47, wildpc-api 120 all pass. Frontend type-checks + builds. Fixed a stale test fixture (secret_env_path kind arg) broken pre-rename.	2026-07-18 22:55:08 -07:00
Paul Payne	d34ff9220d	install.sh: bootstrap Castle's own control plane A fresh clone + ./install.sh set up the infra (Docker, Caddy, MQTT, Postgres) but left the registry empty — so `castle deploy && castle start` brought up nothing. install.sh now gets a person all the way to a running Castle: - ensure_uv + install_cli: install uv and the `castle` CLI (editable from ./cli) so the command exists on a fresh machine. - seed_control_plane: register castle-gateway, castle-api, and the castle dashboard from a new bootstrap/ seed dir, and add `repo:` to castle.yaml so `source: repo:<name>` resolves. Never clobbers existing entries. - build_dashboard: build app/dist/ so the gateway has a UI to serve (best-effort; warns if pnpm is absent). The gateway seed uses a `__SPECS_DIR__` placeholder (no machine-specific paths in the repo), substituted with this machine's specs dir at seed time. .gitignore negates bootstrap/*/castle.yaml so the seeds are tracked despite the user-registry ignore rule. Verified: seeded config loads, derives kinds service/service/static, and renders an off-mode Caddyfile serving the dashboard at :9000/ with /api/ proxied to castle-api.	2026-07-01 16:33:42 -07:00

Author

SHA1

Message

Date

Paul Payne

05b28cb584

Rename Castle -> Wild PC across the repo

Repo-side rename only (Phases 1-3 of the migration plan); the live box
(~/.castle, systemd units, /data/castle, domains) is a separate cutover.

- Slug `castle` -> `wildpc`: CLI command, module names (wildpc_core/cli/api),
  dist names, entry point `wildpc = wildpc_cli.main:main`.
- Identifiers: CastleConfig/NATSClient/DirError/MDNS -> Wildpc*.
- Env/constants: CASTLE_* -> WILDPC_*; ~/.castle -> ~/.wildpc, castle.yaml ->
  wildpc.yaml, /data/castle -> /data/wildpc.
- Systemd UNIT_PREFIX castle- -> wildpc-; own programs castle-api/gateway/etc.
- Display prose "Castle" -> "Wild PC" in docs, agent-guide files, README, frontend.
- Package dirs and bootstrap yaml renamed via git mv; lockfiles regenerated;
  redundant nested uv.lock files dropped (workspace root lock is authoritative).

Tests: core 273, cli 47, wildpc-api 120 all pass. Frontend type-checks + builds.
Fixed a stale test fixture (secret_env_path kind arg) broken pre-rename.

2026-07-18 22:55:08 -07:00

Paul Payne

d34ff9220d

install.sh: bootstrap Castle's own control plane

A fresh clone + ./install.sh set up the infra (Docker, Caddy, MQTT,
Postgres) but left the registry empty — so `castle deploy && castle
start` brought up nothing. install.sh now gets a person all the way to
a running Castle:

- ensure_uv + install_cli: install uv and the `castle` CLI (editable
  from ./cli) so the command exists on a fresh machine.
- seed_control_plane: register castle-gateway, castle-api, and the
  castle dashboard from a new bootstrap/ seed dir, and add `repo:` to
  castle.yaml so `source: repo:<name>` resolves. Never clobbers
  existing entries.
- build_dashboard: build app/dist/ so the gateway has a UI to serve
  (best-effort; warns if pnpm is absent).

The gateway seed uses a `__SPECS_DIR__` placeholder (no machine-specific
paths in the repo), substituted with this machine's specs dir at seed
time. .gitignore negates bootstrap/**/castle.yaml so the seeds are
tracked despite the user-registry ignore rule.

Verified: seeded config loads, derives kinds service/service/static,
and renders an off-mode Caddyfile serving the dashboard at :9000/ with
/api/* proxied to castle-api.

2026-07-01 16:33:42 -07:00

2 Commits