This project was created with Better-T-Stack, a modern TypeScript stack that combines React, TanStack Router, Hono, and more.
- TypeScript - For type safety and improved developer experience
- TanStack Router - File-based routing with full type safety
- TailwindCSS - Utility-first CSS for rapid UI development
- shadcn/ui - Reusable UI components
- Hono - Lightweight, performant server framework
- Bun - Runtime environment
- Turborepo - Optimized monorepo build system
First, install the dependencies:
pnpm installThen, run the development server:
pnpm run devOpen http://localhost:3001 in your browser to see the web application. The API is running at http://localhost:3000.
my-better-t-app/
├── apps/
│ ├── web/ # Frontend application (React + TanStack Router)
│ └── server/ # Backend API (Hono)
├── packages/
pnpm run dev: Start all applications in development modepnpm run build: Build all applicationspnpm run dev:web: Start only the web applicationpnpm run dev:server: Start only the serverpnpm run check-types: Check TypeScript types across all apps
This repository now includes a root render.yaml Blueprint for Render.
It deploys the project as a single Render web service:
- Render builds the Vite frontend in
apps/web - Bun runs
apps/server/src/render.ts - The Hono server serves the built SPA and handles
/api/*on the same origin
This avoids cross-service CORS and public-URL wiring for the browser client.
- Push this repository to GitHub, GitLab, or Bitbucket.
- In Render, open New > Blueprint and select this repository.
- Render will detect
render.yamland prompt you for the secret env vars marked withsync: false. - Create the Blueprint and wait for the first deploy to finish.
DATABASE_URLSUPABASE_URLSUPABASE_SERVICE_ROLE_KEYRESEND_API_KEYEMAIL_FROMVITE_SUPABASE_URLVITE_SUPABASE_ANON_KEY
- The build command sets
VITE_SERVER_URLfrom Render's defaultRENDER_EXTERNAL_URL. - The start command sets
CORS_ORIGINfrom the same Render-provided URL. - Render's health check is configured to use
/healthz. - This setup follows Render's Blueprint, environment-variable, monorepo, and native Node/Bun runtime docs: Render Docs.
Zabbix monitoring assets are available in monitoring/zabbix/README.md.
The server now exposes a protected telemetry endpoint at /api/monitoring/telemetry for:
- rolling average response time under load
- process RSS memory consumption
- normalized CPU utilization
Set MONITORING_TOKEN in the runtime environment before enabling Zabbix polling.