add frontend process service

This commit is contained in:
Yisroel Baum 2026-07-31 10:41:04 +03:00
parent 6da83d87fa
commit 188b300a7f
Signed by: yisroelbaum
GPG key ID: 0FA60884F75520A9
4 changed files with 31 additions and 7 deletions

View file

@ -36,14 +36,19 @@ Install dependencies in a fresh checkout or worktree:
direnv exec "$(git rev-parse --show-toplevel)" npm install
```
Start the development server on the port assigned by the shell hook:
To start only the development server on the port assigned by the shell hook:
```sh
direnv exec "$(git rev-parse --show-toplevel)" \
npm run dev -- --port "$VITE_PORT"
npm run dev -- \
--host 127.0.0.1 \
--port "$VITE_PORT" \
--strictPort
```
`process-compose` does not start or proxy the frontend.
`process-compose` starts the frontend as part of the full development stack.
The frontend remains directly accessible on `VITE_PORT`; Caddy does not proxy
it.
The available validation commands are:

View file

@ -74,12 +74,15 @@ those changes with the most relevant parser, formatter, dry run, or check.
- Run backend commands from `backend/`, or explicitly change into it in the
command. The direnv target remains the worktree root.
- Run frontend commands from `frontend/website/`.
- `process-compose` does not start the frontend. Start it separately with
the worktree's assigned port when needed:
- `process-compose` starts the frontend on the worktree's assigned port. To
start only the frontend:
```sh
direnv exec "$(git rev-parse --show-toplevel)" \
npm run dev -- --port "$VITE_PORT"
npm run dev -- \
--host 127.0.0.1 \
--port "$VITE_PORT" \
--strictPort
```
- When a normally valid check fails because a required service is down,