curl -sSL https://install.nself.org | bash

# Clone nself repository
git clone https://github.com/nself-org/cli.git ~/Sites/nself
cd ~/Sites/nself

# Make executable
chmod +x bin/nself

# Add to PATH
echo 'export PATH="$HOME/Sites/nself/bin:$PATH"' >> ~/.zshrc
source ~/.zshrc

# Check version
nself version

# Run diagnostics
nself doctor

# Expected output:
# ✅ Docker: 24.0.5
# ✅ Docker Compose: v2.20.2
# ✅ Bash: 5.1.16 (or 3.2 on macOS - still compatible)
# ✅ Git: 2.34.1
# ✅ System: Ready

# Navigate to nchat project
cd /Users/admin/Sites/nself-chat

# Create backend directory
mkdir .backend
cd .backend

# Initialize nself project
nself init

# Build configuration
nself build

# Start all services
nself start

# Project Configuration
PROJECT_NAME=nchat
ENV=dev
BASE_DOMAIN=local.nself.org

# PostgreSQL Database
POSTGRES_DB=nchat_db
POSTGRES_USER=postgres
POSTGRES_PASSWORD=your-secure-password-here

# Hasura GraphQL
HASURA_GRAPHQL_ADMIN_SECRET=your-admin-secret-here
HASURA_GRAPHQL_JWT_SECRET={"type":"HS256","key":"your-jwt-secret-min-32-chars-here"}

# Authentication
AUTH_CLIENT_URL=http://localhost:3000  # nchat frontend URL

# Optional Services (recommended for nchat)
REDIS_ENABLED=true                     # For real-time features
NSELF_ADMIN_ENABLED=true               # For backend management
MINIO_ENABLED=true                     # For file uploads (avatars, attachments)
MEILISEARCH_ENABLED=true               # For message search

# Monitoring (optional, useful for production)
MONITORING_ENABLED=false               # Enable in production

# Start all services
nself start

# Stop all services
nself stop

# Restart all services
nself restart

# Check service status
nself status

# View logs
nself logs                # All services
nself logs postgres       # Specific service
nself logs -f             # Follow logs

# Execute commands in containers
nself exec postgres psql -U postgres
nself exec hasura hasura-cli console

# View service URLs
nself urls

# System diagnostics
nself doctor
nself doctor --fix        # Auto-fix issues

# Rebuild after .env changes
nself build

# Force clean rebuild
nself build --force

# Rebuild specific component
nself build --only nginx
nself build --only compose

# 1. Create starter schema from template
nself db schema scaffold basic    # Users, profiles, posts
# OR use nchat-specific schema
nself db schema scaffold saas     # Organizations, members, projects

# 2. Edit schema.dbml (or use dbdiagram.io)
# Design your nchat schema with:
# - users table
# - channels table
# - messages table
# - roles and permissions
# etc.

# 3. Apply everything in one command
nself db schema apply schema.dbml
# This does: import → migrate → seed

# Check migration status
nself db migrate status

# Run pending migrations
nself db migrate up

# Create new migration
nself db migrate create add_channels_table

# Rollback last migration
nself db migrate down

# Fresh migration (dev only, destructive!)
nself db migrate fresh

# Seed database (environment-aware)
nself db seed

# Seed only users
nself db seed users
# Local: Creates 20 test users
# Staging: Creates 100 QA users
# Production: Only explicit users from config

# Generate mock data (reproducible)
nself db mock auto --seed 12345

# Generate TypeScript types from schema
nself db types typescript --output ../src/types/db

# Generate Go structs
nself db types go --output ../backend/models

# Generate Python dataclasses
nself db types python --output ../backend/models

# Interactive PostgreSQL shell
nself db shell

# Execute SQL query
nself db query "SELECT * FROM users LIMIT 10"

# Database inspection
nself db inspect              # Overview
nself db inspect size         # Table sizes
nself db inspect slow         # Slow query analysis

# Backup and restore
nself db backup               # Create backup
nself db backup --name pre-migration
nself db restore latest       # Restore from latest backup

# In .env
MONITORING_ENABLED=true

# Local development
ENV=dev

# Staging/QA
ENV=staging

# Production
ENV=production

# Create staging environment
nself env create staging staging

# Create production environment
nself env create prod production

# List environments
nself env list

# Switch environment
nself env switch staging

# Morning: Start backend
cd .backend
nself start

# Check everything is running
nself status

# Open Hasura console for GraphQL development
open https://api.local.nself.org/console

# View real-time logs (in separate terminal)
nself logs -f

# Evening: Stop backend (optional, can leave running)
nself stop

# 1. Edit schema.dbml or create migration
nself db migrate create add_message_reactions

# 2. Edit the migration file
vim nself/migrations/XXXXXX_add_message_reactions.up.sql

# 3. Run migration
nself db migrate up

# 4. Verify in Hasura console
open https://api.local.nself.org/console

# 5. Generate TypeScript types
nself db types typescript --output ../src/types/db

# 1. Edit .env
echo "CS_1=notifications:express-js:3001" >> .env

# 2. Rebuild
nself build

# 3. Service code is generated in services/notifications/

# 4. Customize the service
cd services/notifications
# Edit src/index.js

# 5. Restart to apply changes
nself restart

# Backend URLs (via nself CLI)
NEXT_PUBLIC_GRAPHQL_URL=http://api.local.nself.org/v1/graphql
NEXT_PUBLIC_AUTH_URL=http://auth.local.nself.org/v1/auth
NEXT_PUBLIC_STORAGE_URL=http://storage.local.nself.org/v1/storage

# Dev Mode
NEXT_PUBLIC_USE_DEV_AUTH=false  # Use real nself auth

# 1. Check Docker is running
docker ps

# 2. Run diagnostics
nself doctor

# 3. Check logs
nself logs --tail 50

# 4. Try clean start
nself stop
nself start --fresh

# Check which service is using a port
lsof -i :5432  # PostgreSQL
lsof -i :8080  # Hasura
lsof -i :3000  # Next.js (your frontend)

# Change port in .env
POSTGRES_PORT=5433

# Rebuild and restart
nself build && nself start

# 1. Check PostgreSQL is healthy
nself status postgres

# 2. Test connection
nself exec postgres psql -U postgres -d nchat_db

# 3. Check Hasura can connect
nself logs hasura

# 4. Verify connection string
nself config show | grep DATABASE_URL

# Trust local certificates
nself trust

# Or manually
cd .backend/ssl/certificates/localhost
sudo security add-trusted-cert -d -r trustRoot -k /Library/Keychains/System.keychain fullchain.pem

# Check PATH
echo $PATH | grep nself

# Add to PATH (zsh)
echo 'export PATH="$HOME/Sites/nself/bin:$PATH"' >> ~/.zshrc
source ~/.zshrc

# Add to PATH (bash)
echo 'export PATH="$HOME/Sites/nself/bin:$PATH"' >> ~/.bashrc
source ~/.bashrc

# 1. Check Hasura is running
nself status hasura

# 2. Check admin secret
nself config show | grep HASURA_GRAPHQL_ADMIN_SECRET

# 3. Restart Hasura
nself restart hasura

# 4. Open console with correct URL
open https://api.local.nself.org/console

# 1. Check resource usage
docker stats

# 2. Increase Docker resources
# Docker Desktop → Settings → Resources → Memory (8GB recommended)

# 3. Disable monitoring if not needed
# In .env:
MONITORING_ENABLED=false
nself build && nself restart

# ESSENTIAL COMMANDS
nself start              # Start all services
nself stop               # Stop all services
nself status             # Check service health
nself logs -f            # Follow logs
nself urls               # Show all service URLs

# DATABASE
nself db migrate up      # Run migrations
nself db seed            # Seed database
nself db types typescript # Generate types
nself db shell           # PostgreSQL shell

# DEVELOPMENT
nself build              # Rebuild config
nself restart hasura     # Restart specific service
nself exec postgres psql # Execute in container

# TROUBLESHOOTING
nself doctor             # Run diagnostics
nself doctor --fix       # Auto-fix issues
nself start --fresh      # Clean start