Compare commits

..

No commits in common. "76df3d645b9aee9a13bb116d4ddd2206153b9931" and "6da83d87fa3fd10a3f568edd0b64fe3c3a092484" have entirely different histories.

4 changed files with 7 additions and 31 deletions

View file

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

View file

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

View file

@ -124,5 +124,4 @@ if [ ! -e "$REPO_ROOT/backend/public/storage" ]; then
(cd "$REPO_ROOT/backend" && php artisan storage:link) (cd "$REPO_ROOT/backend" && php artisan storage:link)
fi fi
echo "[dev] run 'process-compose up' to start:" \ echo "[dev] run 'process-compose up' to start postgres + mailpit + backend + caddy"
"postgres + mailpit + backend + caddy + frontend"

View file

@ -44,21 +44,6 @@ processes:
initial_delay_seconds: 2 initial_delay_seconds: 2
period_seconds: 10 period_seconds: 10
frontend:
command: >-
npm run dev --
--host 127.0.0.1
--port ${VITE_PORT:-5173}
--strictPort
working_dir: ./frontend/website
readiness_probe:
http_get:
host: 127.0.0.1
port: ${VITE_PORT:-5173}
path: /
initial_delay_seconds: 1
period_seconds: 2
caddy: caddy:
command: caddy run --config Caddyfile --adapter caddyfile command: caddy run --config Caddyfile --adapter caddyfile
depends_on: depends_on: