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	c5cf3a1561	feat(core): kind-scoped deployment identity (name, kind) A deployment's identity becomes (name, kind), so a tool, service, and job can share a name (a `backup` trio). Kind is structural — which per-kind store / dir — not a derived discriminator threaded around. - CastleConfig holds per-kind stores (services/jobs/tools/statics/references); all_deployments()/deployments_named()/deployment(kind,name) replace the single flat `deployments` dict. A construction-only `deployments` InitVar routes a flat map into the stores by kind_for. - Storage: deployments/<store>/<name>.yaml (per-kind dirs), with read-compat for the old flat + services/+jobs/ layouts. - Registry keyed by composite "<kind>/<name>" + name field; get()/all()/named()/put(). - Job units carry a -job marker (castle-<name>-job.{service,timer}); services and everything else unchanged — so a service and a job can coexist. - deploy/apply/lifecycle thread kind through unit naming, activate/deactivate, is_active; caddyfile/tunnel/relations iterate via all_deployments/registry.all. - Subdomain uniqueness validated across kinds (a service and a static can't share one). 182 core tests pass, incl. a new same-name-trio suite (round-trip, distinct units, subdomain guard). API/CLI/UI updated in follow-up phases.	2026-07-06 02:25:05 -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

c5cf3a1561

feat(core): kind-scoped deployment identity (name, kind)

A deployment's identity becomes (name, kind), so a tool, service, and job can
share a name (a `backup` trio). Kind is structural — which per-kind store / dir —
not a derived discriminator threaded around.

- CastleConfig holds per-kind stores (services/jobs/tools/statics/references);
  all_deployments()/deployments_named()/deployment(kind,name) replace the single
  flat `deployments` dict. A construction-only `deployments` InitVar routes a flat
  map into the stores by kind_for.
- Storage: deployments/<store>/<name>.yaml (per-kind dirs), with read-compat for
  the old flat + services/+jobs/ layouts.
- Registry keyed by composite "<kind>/<name>" + name field; get()/all()/named()/put().
- Job units carry a -job marker (castle-<name>-job.{service,timer}); services and
  everything else unchanged — so a service and a job can coexist.
- deploy/apply/lifecycle thread kind through unit naming, activate/deactivate,
  is_active; caddyfile/tunnel/relations iterate via all_deployments/registry.all.
- Subdomain uniqueness validated across kinds (a service and a static can't share one).

182 core tests pass, incl. a new same-name-trio suite (round-trip, distinct units,
subdomain guard). API/CLI/UI updated in follow-up phases.

2026-07-06 02:25:05 -07:00

2 Commits