Remove frontend errors and app passthrough (#251)

This commit is contained in:
Nathan Flurry 2026-03-13 21:14:31 -07:00 committed by GitHub
parent d8b8b49f37
commit 8fb19b50da
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
23 changed files with 146 additions and 1119 deletions

View file

@ -50,6 +50,11 @@ Use `pnpm` workspaces and Turborepo.
- `compose.dev.yaml` loads `foundry/.env` (optional) for credentials needed by the backend (GitHub OAuth, Stripe, Daytona, API keys, etc.).
- The canonical source for these credentials is `~/misc/the-foundry.env`. If `foundry/.env` does not exist, copy it: `cp ~/misc/the-foundry.env foundry/.env`
- `foundry/.env` is gitignored and must never be committed.
- If your changes affect the dev server, mock server, frontend runtime, backend runtime, Vite wiring, compose files, or other server-startup/runtime behavior, you must start or restart the relevant stack before finishing the task.
- Use the matching stack for verification:
- real backend + frontend changes: `just foundry-dev` or restart with `just foundry-dev-down && just foundry-dev`
- mock frontend changes: `just foundry-mock` or restart with `just foundry-mock-down && just foundry-mock`
- local frontend-only work outside Docker: restart `pnpm --filter @sandbox-agent/foundry-frontend dev` or `just foundry-dev-mock` as appropriate
- The backend does **not** hot reload. Bun's `--hot` flag causes the server to re-bind on a different port (e.g. 6421 instead of 6420), breaking all client connections while the container still exposes the original port. After backend code changes, restart the backend container: `just foundry-dev-down && just foundry-dev`.
## Railway Logs