@haus-tech/haus-workflow 0.26.0 → 0.26.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md
CHANGED
|
@@ -34,7 +34,7 @@ Specify the least. Infer the rest from the repo's stack + these conventions, and
|
|
|
34
34
|
|
|
35
35
|
- **IMPORTANT — never install anything without asking first; global/system tools especially** (Homebrew, Docker, Laravel Herd, global `npm`/`composer` packages). Detect what's already present; if something required is missing, name it, say why it's needed, and get an explicit **yes** before installing. Prefer the least-invasive option, and don't switch or override tools the dev already has.
|
|
36
36
|
- **PHP / WordPress sites are served by the developer's own PHP environment.** If they already have one — detect `valet`, `herd`, `ddev`, or `php` on PATH — **use it**: just satisfy the env contract (docroot → the repo's `web/`, HTTPS) and report the URL; never override what they already run. **Only when no local PHP environment exists** (a completely fresh machine) suggest installing **[Laravel Herd](https://herd.laravel.com)** as the default (asking first) and point its docroot at `web/` + `herd secure`.
|
|
37
|
-
- **Databases and other services (a repo's `needs:`) run in Docker as
|
|
37
|
+
- **Databases and other services (a repo's `needs:`) run in Docker as a shared, workspace-owned `docker-compose` project** — grouped and self-contained (`up`/`down` together, named volumes), namespaced per workspace instance via `COMPOSE_PROJECT_NAME` + its own host ports so the workspace can run multiple times side by side. Image/port/env per the house convention (`mysql:8`, `postgres:16`, …). Don't reuse a repo's own compose that bind-mounts repo-relative init files (`seed.sql`) — author the service in the workspace compose. Services come up **empty** (seeding is the separate `seed:` step); record chosen host ports in the workspace `localdev.yml` `env` map.
|
|
38
38
|
- **Dependencies** install from the lockfile (Step 3).
|
|
39
39
|
- A repo's `localdev.yml` carries **only what can't be inferred** — its `needs`, repo-specific `build`/`seed` commands, env keys, and URL. Detect the stack (e.g. Bedrock = `composer.json` + `web/` docroot + `wp-cli.yml`; Vendure/Node = `docker-compose.yml` + `@vendure/*`) and apply the matching convention.
|
|
40
40
|
|
|
@@ -84,7 +84,7 @@ env:
|
|
|
84
84
|
1. **Discover** `.haus-workflow/localdev.yml` in the workspace root and each repo.
|
|
85
85
|
2. **Resolve order** from the workspace `order` (repos not listed run last, in manifest order). No workspace file → manifest order.
|
|
86
86
|
3. **Per repo, in order**, apply intent via the conventions:
|
|
87
|
-
- **`needs`** →
|
|
87
|
+
- **`needs`** → add the service to the **workspace compose project** and `docker compose up -d` if not already running (namespaced by `COMPOSE_PROJECT_NAME`, free host ports per instance; not the repo's own bind-mounting compose). Comes up **empty**; record host ports in the workspace `localdev.yml` `env` map — data lands in `seed:`.
|
|
88
88
|
- **`build`** → run it (honor any node version the repo's docs note).
|
|
89
89
|
- **`serve`** → for `via: herd` / PHP envs, install nothing — verify the dev's environment serves `web/`, and report the URL.
|
|
90
90
|
- **`seed`** → populate the empty datastore. **Always a distinct, confirm-gated step, separate from `needs:` bring-up** (don't conflate "DB up" with "DB has data"). Before running, **check its prerequisites and report any gap instead of running blind** — e.g. WP-CLI present (for `wp` / `db:pull` seeds), the target repo's **`.env` written** (the seed reads connection values from it — done in the Env step above), the **SSH alias resolves** (for remote pulls like `dep db:pull staging-oderland`). **Confirm first** for every remote (SSH) or destructive (overwrites data) seed — every run, even on re-run. Missing prerequisite → skip with a clear message, don't guess.
|
|
@@ -112,13 +112,13 @@ env:
|
|
|
112
112
|
- **Yes** → start each repo in the workspace `order` (its `serve.start`, e.g. `yarn dev`; bring up any remaining foreground services), run any follow-ups (e.g. `wp sync-products sync`), then **print the live URLs** (each repo's `serve.url`).
|
|
113
113
|
- **No** → just print the ordered start commands + follow-ups as next steps; start nothing.
|
|
114
114
|
|
|
115
|
-
**Default is "ready to run" (D2):** the preparation — datastores up (
|
|
115
|
+
**Default is "ready to run" (D2):** the preparation — datastores up (workspace `docker compose` project), seeds applied (confirm-gated), links, builds, each repo's `.env` written — always happens. Starting the **foreground** dev servers and the initial product sync happen **only if the user says yes** to the start prompt above; otherwise they're printed, not run.
|
|
116
116
|
|
|
117
117
|
## Step 5 — Report and define "done"
|
|
118
118
|
|
|
119
119
|
**"Done" is an explicit terminal state**, not "looks set up". The preparation reaches:
|
|
120
120
|
|
|
121
|
-
- datastores up (
|
|
121
|
+
- datastores up (workspace `docker compose` project),
|
|
122
122
|
- dependencies installed and builds green,
|
|
123
123
|
- links wired,
|
|
124
124
|
- each repo's `.env` written from known values.
|