Add tera-web (Next.js frontend) to Render Blueprint#105
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c293c5cf92
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| plan: starter | ||
| buildCommand: pnpm install --no-frozen-lockfile && pnpm build | ||
| startCommand: pnpm start | ||
| healthCheckPath: /health |
There was a problem hiding this comment.
The new tera-web service uses healthCheckPath: /health, but this repo’s Next.js app does not define a /health route (the only health-related frontend route is app/api/admin/health/route.ts, which is under /api/admin/health). In Render, this means health probes for tera-web will return 404 and can keep deploys unhealthy even when the app is otherwise running.
Useful? React with 👍 / 👎.
1 participant
Adds tera-web alongside tera-api in render.yaml. Both deploy from the same repo — Render handles them as separate services.