Shisha Log

A full-stack application for tracking and managing shisha (hookah) sessions.

Project Structure

shisha-log/
├── backend/               # Go backend API
├── frontend/              # React frontend SPA
├── infra/                 # Terraform infrastructure
├── docs/                  # Documentation
├── .env                  # All environment variables (frontend + backend)
├── .env.example          # Example configuration
└── Makefile              # Project commands

Quick Start

1. Setup environment files

   make setup-env
   # Edit .env with your configuration

2. Install dependencies

   make install

3. Run development servers

   # In separate terminals:
   make backend-dev    # Backend on http://localhost:8080
   make frontend-dev   # Frontend on https://localhost:5173

Available Commands

Run make help to see all available commands:

• Development: backend-dev, frontend-dev
• Build: backend-build, frontend-build
• Deploy: deploy-frontend, deploy-all (backend deploys via Kubernetes manifests)
• Infrastructure: infra-init, infra-plan, infra-apply

Environment Files

Single environment file in the project root:

• .env - All configuration (frontend VITE_* and backend settings)
• .env.example - Example configuration with all required variables

Deployment

The application uses separate domains for frontend and backend:

• Frontend: S3 + CloudFront (https://shisha.toof.jp)
• Backend: GKE (Kubernetes) behind HTTPS load balancing (https://api.shisha.toof.jp)
• Database: PostgreSQL via Supabase, with backups managed in AWS Lambda/S3

Kubernetes fetches credentials from Google Cloud Secret Manager through External Secrets Operator. Use secretstore-gcpsm.yaml and bootstrap-gcp-secrets.sh to keep GSM in sync with .env secrets.

See docs/ for detailed deployment guides.

Documentation

• API Documentation
• Infrastructure Architecture
• DNS Configuration Guide
• Frontend Specifications
• Backend Deployment
• Backend Setup Guides