Impact Circle

A trust-based platform for community impact.

Tech Stack • Structure • Getting Started • Deployment

---

🚀 Tech Stack

• Monorepo Management: Turborepo
• Frontend: Next.js (App Router, React 19)
• Backend: Hono (Node.js runtime)
• Database: Drizzle ORM with PostgreSQL
• Auth: Better Auth
• Styling: Tailwind CSS & Shadcn UI
• State Management: Zustand & React Query

📁 Project Structure

.
├── apps/
│   ├── web/          # Next.js frontend
│   └── backend/      # Hono API server (bundled with tsup)
├── packages/
│   ├── db/           # Drizzle schema & database client
│   ├── ui/           # Shared Shadcn UI components
│   └── typescript-config/ # Shared TS configurations
├── deploy-gcp.sh     # Interactive GCP deployment script
└── turbo.json        # Turborepo configuration

🛠️ Getting Started

Prerequisites

• pnpm (v10+)
• Google Cloud CLI (for deployment)

Local Development

1. Install dependencies:

   pnpm install

2. Setup environment variables: Create .env.production in both apps/web and apps/backend (or use local .env files).

3. Run development servers:

   pnpm dev

   • Frontend: http://localhost:3000
   • Backend: http://localhost:8080

🚢 Deployment (Google Cloud)

We use an automated script to deploy both services to Google Cloud Run.

# Deploy everything
./deploy-gcp.sh <PROJECT_ID>

# Deploy only the web app
./deploy-gcp.sh <PROJECT_ID> --web-only

# Deploy only the backend
./deploy-gcp.sh <PROJECT_ID> --backend-only

Deployment Features

• Zero-Config Env Loading: Automatically sources credentials from .env.production files.
• Tsup Bundling: Backend is bundled into a single file to eliminate monorepo pathing issues in Docker.
• Standalone Mode: Frontend uses Next.js standalone output for optimized container sizes.

---

Built with ❤️ for community impact.