wehub-resource-sync
98e40dac97
CLI Smoke Test / smoke-test-linux (20) (push) Waiting to run
CLI Smoke Test / smoke-test-linux (24) (push) Waiting to run
CLI Smoke Test / smoke-test-windows (20) (push) Waiting to run
CLI Smoke Test / smoke-test-windows (24) (push) Waiting to run
Expo App TypeScript typecheck / typecheck (push) Waiting to run
81 lines
2.1 KiB
Markdown
81 lines
2.1 KiB
Markdown
# Dev Environments
|
|
|
|
This document covers the local environment manager in [`environments/environments.ts`](../environments/environments.ts).
|
|
|
|
## What `pnpm env:*` Does
|
|
|
|
- `pnpm env:new`: create a new isolated environment under `environments/data/envs/<name>`.
|
|
- `pnpm env:use <name>`: switch the current environment.
|
|
- `pnpm env:server`: run the server inside the current environment.
|
|
- `pnpm env:web`: run the web app inside the current environment.
|
|
- `pnpm env:cli`: run the CLI inside the current environment.
|
|
|
|
Each environment injects its own:
|
|
|
|
- `HAPPY_HOME_DIR`
|
|
- `HAPPY_SERVER_URL`
|
|
- `HAPPY_WEBAPP_URL`
|
|
- `HAPPY_PROJECT_DIR`
|
|
- Expo/server port settings
|
|
- dev auth values when seeded
|
|
|
|
Each fresh environment also gets a copied lightweight fixture project from
|
|
`environments/lab-rat-todo-project/` at `environments/data/envs/<name>/project`.
|
|
|
|
Current limitation: the lab-rat project is copied as plain files only. It does
|
|
not include git history yet, so provider tests that depend on realistic repo
|
|
history still need a later fixture upgrade.
|
|
|
|
## `pnpm env:cli` Is A Passthrough
|
|
|
|
`pnpm env:cli` forwards extra arguments directly to `happy`.
|
|
|
|
Examples:
|
|
|
|
```bash
|
|
pnpm env:cli --help
|
|
pnpm env:cli codex
|
|
pnpm env:cli daemon status
|
|
pnpm env:cli daemon stop
|
|
pnpm env:cli daemon start
|
|
```
|
|
|
|
This is equivalent to sourcing the environment and running the CLI manually:
|
|
|
|
```bash
|
|
source environments/data/envs/<name>/env.sh
|
|
happy daemon status
|
|
```
|
|
|
|
## Why `env:cli` Exists
|
|
|
|
It is a convenience wrapper for the current environment. It does not create or pick an environment on its own. It just:
|
|
|
|
1. Reads `environments/data/current.json`
|
|
2. Builds env vars for that environment
|
|
3. Launches the CLI with those vars applied
|
|
|
|
If you want a lower-level, shell-native workflow, use the generated env file directly:
|
|
|
|
```bash
|
|
source environments/data/envs/<name>/env.sh
|
|
happy
|
|
```
|
|
|
|
## Restarting The Current Environment Daemon
|
|
|
|
Either of these now works:
|
|
|
|
```bash
|
|
pnpm env:cli daemon stop
|
|
pnpm env:cli daemon start
|
|
```
|
|
|
|
Or:
|
|
|
|
```bash
|
|
source environments/data/envs/<name>/env.sh
|
|
happy daemon stop
|
|
happy daemon start
|
|
```
|