feat: setup CI/CD

Author: kronosapiens

.github/workflows/ci.yml

@@ -0,0 +1,48 @@
+name: Build and Test
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  ci:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Setup pnpm
+        uses: pnpm/action-setup@v4
+        with:
+          version: 10
+          run_install: false
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 22
+
+      - name: Get pnpm store directory
+        shell: bash
+        run: echo "STORE_PATH=$(pnpm store path --silent)" >> $GITHUB_ENV
+
+      - name: Cache pnpm store
+        uses: actions/cache@v4
+        with:
+          path: ${{ env.STORE_PATH }}
+          key: pnpm-store-${{ runner.os }}-${{ hashFiles('pnpm-lock.yaml') }}
+          restore-keys: pnpm-store-${{ runner.os }}-
+
+      - name: Install dependencies
+        run: pnpm install --frozen-lockfile
+
+      - name: Lint
+        run: pnpm --filter backend lint
+
+      - name: Type check
+        run: pnpm --filter backend typecheck
+
+      - name: Test
+        run: pnpm --filter backend test

.gitignore

@@ -5,7 +5,6 @@
 /.pnp
 .pnp.js
 .pnpm-store
-pnpm-lock.yaml
 
 # testing
 /coverage

README.md

@@ -10,3 +10,45 @@ Progression: Kōhai → Senpai → Sensei based on peer recognition.
 
 ### [Blockchain Roles](./spec/BLOCKCHAIN.md)
 Wallet-linked roles based on Starknet state (NFT ownership, token holdings, etc.).
+
+## Deployment
+
+The bot uses GitHub Actions for CI and Railway for deployment.
+Pushes to `main` automatically deploy after CI passes.
+
+### Setup
+
+1. **Create Railway Project**
+   - Go to [railway.app](https://railway.app) and sign in with GitHub
+   - Click "New Project" → "Deploy from GitHub repo"
+   - Select the `daimyo` repository
+
+2. **Set Environment Variables**
+   - In Railway, go to your service → Variables
+   - Add the following (see `backend/.env.example` for reference):
+     ```
+     DISCORD_BOT_TOKEN=<your token>
+     DISCORD_GUILD_ID=<your guild id>
+     DISCORD_CLIENT_ID=<your client id>
+     DOJO_EMOJI_NAME=dojo
+     KOHAI_ROLE_ID=<role id>
+     SENPAI_ROLE_ID=<role id>
+     SENSEI_ROLE_ID=<role id>
+     DATABASE_PATH=/data/daimyo.db
+     DECAY_WINDOW_DAYS=360
+     SENPAI_REACTION_THRESHOLD=50
+     SENPAI_UNIQUE_PERCENT=0.10
+     SENSEI_REACTION_THRESHOLD=30
+     SENSEI_UNIQUE_PERCENT=0.20
+     ```
+
+3. **Create Volume for Database**
+   - In Railway, click your service → Settings → Volumes
+   - Add a volume with mount path `/data`
+   - This persists the SQLite database across deployments
+
+4. **(Optional) GitHub Branch Protection**
+   - Go to GitHub repo → Settings → Branches
+   - Add rule for `main` branch
+   - Enable "Require status checks to pass before merging"
+   - Select the `ci` check

backend/package.json

@@ -1,12 +1,13 @@
 {
-  "name": "daimyo-backend",
+  "name": "backend",
   "version": "1.0.0",
   "description": "Discord reputation bot for Dojo community",
   "main": "dist/index.js",
   "type": "module",
   "scripts": {
     "dev": "tsx watch src/index.ts",
-    "build": "tsc",
+    "build": "tsc -p tsconfig.build.json",
+    "typecheck": "tsc --noEmit -p tsconfig.build.json",
     "start": "node dist/index.js",
     "deploy-commands": "tsx src/deploy-commands.ts",
     "lint": "eslint .",