You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Isolation is via per-instance DB + Temporal namespace/task queue + Kafka topic suffixing + instance-scoped Kafka consumer groups/client IDs (not per-instance infra containers).
45
55
- The workspace can have an **active instance** (stored in `.shipsec-instance`, gitignored).
56
+
- Instance env files are stored at `.instances/instance-N/{backend,worker,frontend}.env` and can be managed with `just instance-env ...`.
46
57
47
58
**Agent rule:** before running any dev commands, ensure you’re targeting the intended instance.
48
59
49
60
- Always check: `just instance show`
50
61
- If the task is ambiguous (logs, curl, E2E, “run locally”, etc.), ask the user which instance to use.
51
62
- If the user says “use instance N”, prefer either:
52
63
-`just instance use N` then run `just dev` / `bun run test:e2e`, or
53
-
- explicit instance invocation (`just dev N ...`) for one-off commands.
64
+
- explicit env override (`SHIPSEC_INSTANCE=N just dev ...`) for one-off commands.
54
65
55
66
**Ports / URLs**
56
67
@@ -61,7 +72,7 @@ Local development runs as **multiple app instances** (PM2) on top of **one share
61
72
**E2E tests**
62
73
63
74
- E2E targets the backend for `SHIPSEC_INSTANCE` (or the active instance).
64
-
- When asked to run E2E, confirm the instance and ensure that instance is running: `just dev N start`.
75
+
- When asked to run E2E, confirm the instance and ensure that instance is running: `SHIPSEC_INSTANCE=N just dev start` (or `just instance use N` then `just dev start`).
Each instance gets its own frontend port, backend port, database, and Temporal namespace while sharing a single Docker infra stack. See [Multi-Instance Development Guide](docs/MULTI-INSTANCE-DEV.md) for full details.
0 commit comments