@crossdelta/platform-sdk 0.12.0 → 0.13.1

package/bin/templates/workspace/infra/services/nats.ts.hbs

@@ -1,55 +0,0 @@
-import type { K8sServiceConfig } from '@crossdelta/infrastructure'
-
-/**
- * NATS message broker configuration.
- *
- * Provides event-driven communication via CloudEvents and JetStream.
- *
- * Internal-only service - accessed via cluster DNS:
- * nats://nats.{{projectName}}.svc.cluster.local:4222
- *
- * Local development:
- * nats://localhost:4222
- */
-const config: K8sServiceConfig = {
-  name: 'nats',
-  containerPort: 4222,
-  replicas: 1,
-  image: 'nats:2.10-alpine',
-  command: ['-c', '/etc/nats/nats.prod.conf'],
-  healthCheck: {
-    port: 8222,
-    path: '/healthz',
-  },
-  resources: {
-    requests: { cpu: '50m', memory: '128Mi' },
-    limits: { cpu: '200m', memory: '256Mi' },
-  },
-  volumes: [
-    {
-      name: 'nats-config',
-      configMap: 'nats-config',
-      mountPath: '/etc/nats',
-    },
-    {
-      name: 'nats-data',
-      persistentVolumeClaim: 'nats-data',
-      mountPath: '/data',
-    },
-  ],
-  env: {
-    // Authentication for production
-    NATS_USER: process.env.NATS_USER || 'admin',
-    NATS_PASSWORD: process.env.NATS_PASSWORD || 'changeme',
-  },
-  // Expose monitoring port (internal only)
-  additionalPorts: [
-    {
-      name: 'http',
-      port: 8222,
-      targetPort: 8222,
-    },
-  ],
-}
-
-export default config

package/bin/templates/workspace/services/nats/README.md

@@ -1,107 +0,0 @@
-# NATS Message Broker
-
-> 🚀 **Event-driven communication** powered by NATS + JetStream
-
-Message broker for CloudEvents-based microservices communication using [`@crossdelta/cloudevents`](https://github.com/crossdelta/platform/tree/main/packages/cloudevents).
-
-## ⚡ Quick Start
-
-```bash
-# Start NATS in Docker (auto-started with `bun dev`)
-bun run start:dev
-
-# Check health
-curl http://localhost:8222/healthz
-
-# View JetStream status
-curl http://localhost:8222/jsz
-```
-
-## 🔌 Connecting to NATS
-
-Services connect via environment variables:
-
-| Environment | URL | Description |
-|-------------|-----|-------------|
-| **Local** | `nats://localhost:4222` | Docker container |
-| **Kubernetes** | `nats://nats.<namespace>.svc.cluster.local:4222` | Internal service DNS |
-
-**Example:**
-```typescript
-import { publish } from '@crossdelta/cloudevents'
-
-await publish('orders.created', { orderId: 'ord_123', total: 99.99 })
-```
-
-## 📊 Monitoring & Health Checks
-
-NATS exposes HTTP endpoints for monitoring:
-
-| Endpoint | Purpose |
-|----------|---------|
-| `http://localhost:8222/healthz` | Health check (`{"status":"ok"}`) |
-| `http://localhost:8222/jsz` | JetStream statistics (streams, consumers, messages) |
-| `http://localhost:8222/varz` | Server variables (connections, memory, uptime) |
-| `http://localhost:8222/connz` | Active connections |
-
-## 🗄️ JetStream Persistence
-
-JetStream provides durable event streaming with at-least-once delivery:
-
-- **Local Dev:** `.nats-data/` directory (git-ignored)
-- **Production:** Persistent volume mounted at `/data`
-- **Streams:** Auto-created by `@crossdelta/cloudevents` consumer setup
-
-**Stream Configuration:**
-- Retention: Interest-based (messages deleted after all consumers ack)
-- Deduplication: 2-minute window
-- Max message age: 24 hours (configurable via `nats.prod.conf`)
-
-## 🛠️ Configuration
-
-### Local Development (`nats.conf`)
-- JetStream enabled with local file storage
-- No authentication (Docker network isolation)
-- Ports: 4222 (client), 8222 (HTTP monitoring)
-
-### Production (`nats.prod.conf`)
-- Token-based authentication (via `NATS_TOKEN` env var)
-- Persistent storage at `/data`
-- Resource limits configured via Kubernetes
-
-## 📦 Environment Variables
-
-Generated automatically in `.env.local` via `bun dev`:
-
-```bash
-NATS_PORT=4222                # Client port
-NATS_HTTP_PORT=8222           # HTTP monitoring port
-NATS_IMAGE=nats:2.10-alpine   # Docker image
-```
-
-## 🐳 Docker Commands
-
-```bash
-# Start (via npm script)
-bun run start:dev
-
-# Manual start
-docker run -d --name my-nats \
-  -p 4222:4222 -p 8222:8222 \
-  -v $(pwd)/.nats-data:/data \
-  -v $(pwd)/nats.conf:/etc/nats/nats.conf:ro \
-  nats:2.10-alpine -c /etc/nats/nats.conf
-
-# View logs
-docker logs -f my-nats
-
-# Stop & remove
-docker rm -f my-nats
-```
-
-## 📚 Learn More
-
-- [NATS Documentation](https://docs.nats.io/)
-- [JetStream Guide](https://docs.nats.io/nats-concepts/jetstream)
-- [`@crossdelta/cloudevents` Package](https://github.com/crossdelta/platform/tree/main/packages/cloudevents)
-- [CloudEvents Specification](https://cloudevents.io/)

package/bin/templates/workspace/services/nats/nats.conf

@@ -1,31 +0,0 @@
-# NATS Server Configuration
-# Used by both local development and production
-# See: https://docs.nats.io/running-a-nats-service/configuration
-
-# Server identification
-server_name: nats
-
-# Client connections
-listen: 0.0.0.0:4222
-
-# HTTP monitoring
-http: 0.0.0.0:8222
-
-# JetStream configuration
-jetstream {
-  # Store directory for persistence
-  # Local: mounted from .nats-data/
-  # Production: mounted from DO Volume
-  store_dir: /data/jetstream
-
-  # Memory storage limit (1GB)
-  max_mem_store: 1Gb
-
-  # File storage limit (10GB - matches DO Volume size)
-  max_file_store: 10Gb
-}
-
-# Logging
-debug: false
-trace: false
-logtime: true

package/bin/templates/workspace/services/nats/nats.prod.conf

@@ -1,27 +0,0 @@
-# NATS Server Configuration - Production
-# Includes authentication for secure public access
-# See: https://docs.nats.io/running-a-nats-service/configuration
-
-# Server identification
-server_name: nats
-
-# Client connections
-listen: 0.0.0.0:4222
-
-# HTTP monitoring (internal only)
-http: 127.0.0.1:8222
-
-# Authentication - required for production
-# Env vars: NATS_USER, NATS_PASSWORD
-authorization {
-  user: $NATS_USER
-  password: $NATS_PASSWORD
-  timeout: 5
-}
-
-# JetStream configuration
-jetstream {
-  store_dir: /data/jetstream
-  max_mem: 256M
-  max_file: 2G
-}

package/bin/templates/workspace/services/nats/package.json.hbs

@@ -1,7 +0,0 @@
-{
-  "name": "@{{projectName}}/nats",
-  "private": true,
-  "scripts": {
-    "start:dev": "./scripts/start-dev.sh"
-  }
-}

package/bin/templates/workspace/services/nats/scripts/start-dev.sh.hbs

@@ -1,55 +0,0 @@
-#!/bin/bash
-set -euo pipefail
-
-# Load environment variables from root .env.local
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-ROOT_DIR="$SCRIPT_DIR/../../.."
-ENV_FILE="$ROOT_DIR/.env.local"
-
-if [[ -f "$ENV_FILE" ]]; then
-  set -a
-  source "$ENV_FILE"
-  set +a
-else
-  echo "[NATS] Warning: $ENV_FILE not found. Run 'pf dev' or your package manager's 'generate-env' script first."
-fi
-
-# Container name (local dev only)
-CONTAINER_NAME="{{projectName}}-nats"
-
-# Ports from .env.local (generated from infra/services/nats.ts)
-NATS_PORT="${NATS_PORT:-4222}"
-NATS_HTTP_PORT="${NATS_HTTP_PORT:-8222}"
-NATS_IMAGE="${NATS_IMAGE:-nats:2.10-alpine}"
-
-# Config file (shared between local and production)
-NATS_CONF="$SCRIPT_DIR/../nats.conf"
-
-# Data directory for JetStream persistence (local dev)
-NATS_DATA_DIR="${NATS_DATA_DIR:-$ROOT_DIR/.nats-data}"
-
-# Stop and remove existing container if it exists (ensures clean state)
-if docker ps -a --format '\{{.Names}}' | grep -q "^${CONTAINER_NAME}$"; then
-  echo "[NATS] Removing existing container..."
-  docker rm -f "$CONTAINER_NAME" > /dev/null 2>&1 || true
-fi
-
-# Ensure data directory exists
-mkdir -p "$NATS_DATA_DIR"
-
-# Create new container with shared config file
-# Config file: services/nats/nats.conf (same as production)
-echo "[NATS] Starting with JetStream on ports ${NATS_PORT} (client) and ${NATS_HTTP_PORT} (http)..."
-echo "[NATS] Using config: $NATS_CONF"
-echo "[NATS] Data directory: $NATS_DATA_DIR"
-echo ""
-
-# Start container in foreground (logs streaming) so Turbo keeps watching
-docker run --rm \
-  --name "$CONTAINER_NAME" \
-  -p "${NATS_PORT}:4222" \
-  -p "${NATS_HTTP_PORT}:8222" \
-  -v "${NATS_DATA_DIR}:/data" \
-  -v "${NATS_CONF}:/etc/nats/nats.conf:ro" \
-  "$NATS_IMAGE" \
-  -c /etc/nats/nats.conf