Ali/dev

docs/ai-tools/cursor.mdx → .cursor/rules.md

@@ -1,27 +1,3 @@
----
-title: "Cursor setup"
-description: "Configure Cursor for your documentation workflow"
-icon: "arrow-pointer"
----
-
-Use Cursor to help write and maintain your documentation. This guide shows how to configure Cursor for better results on technical writing tasks and using Mintlify components.
-
-## Prerequisites
-
-- Cursor editor installed
-- Access to your documentation repository
-
-## Project rules
-
-Create project rules that all team members can use. In your documentation repository root:
-
-```bash
-mkdir -p .cursor
-```
-
-Create `.cursor/rules.md`:
-
-````markdown
 # Mintlify technical writing rule
 
 You are an AI writing assistant specialized in creating exceptional technical documentation using Mintlify components and following industry-leading technical writing practices.
@@ -416,5 +392,4 @@ description: "Concise description explaining page purpose and value"
 - Use **Accordions** for progressive disclosure of information
 - Use **RequestExample/ResponseExample** specifically for API endpoint documentation
 - Use **ParamField** for API parameters, **ResponseField** for API responses
-- Use **Expandable** for nested object properties or hierarchical information
-````
+- Use **Expandable** for nested object properties or hierarchical information

.github/workflows/ci.yml

@@ -46,4 +46,26 @@ jobs:
         working-directory: website
         run: pnpm run build
         env:
-          NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY: ${{ secrets.NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY }}
+          NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY: ${{ secrets.NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY }}
+
+  plugin:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 22
+
+      - name: Install dependencies
+        working-directory: plugin
+        run: npm ci
+
+      - name: Typecheck
+        working-directory: plugin
+        run: npm run typecheck
+
+      - name: Run tests
+        working-directory: plugin
+        run: npm test

.github/workflows/deploy.yml

@@ -1,80 +1,65 @@
-name: Deploy Website
+name: Deploy Plugin
 
 on:
-  pull_request:
+  push:
     branches:
       - main
-    types:
-      - opened
-      - synchronize
-      - reopened
+    paths:
+      - 'plugin/**'
 
 concurrency:
-  group: deploy-preview-${{ github.event.pull_request.number }}
+  group: deploy-production
   cancel-in-progress: true
 
 jobs:
   deploy:
     runs-on: ubuntu-latest
 
     steps:
-      - name: Deploy to server
+      - name: Deploy plugin and restart gateway
         uses: appleboy/ssh-action@v1
-        env:
-          NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY: ${{ secrets.NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY }}
         with:
           host: ${{ secrets.SERVER_HOST }}
           username: ${{ secrets.SERVER_USER }}
           key: ${{ secrets.SSH_PRIVATE_KEY }}
-          envs: NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY
           script: |
             set -e
 
-            export NVM_DIR="$HOME/.nvm"
-            [ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"
+            cd ~/loglife
+            git fetch origin
+            git checkout main
+            git reset --hard origin/main
 
-            DEPLOY_DIR="$HOME/loglife-preview"
-            APP_NAME=loglife-preview
-            PORT=3001
-            BRANCH=${{ github.head_ref }}
+            # Restart the gateway so it loads the updated plugin code
+            openclaw gateway restart
 
-            if [ ! -d "$DEPLOY_DIR" ]; then
-              git clone https://github.com/${{ github.repository }}.git "$DEPLOY_DIR"
-            fi
+            # Wait for gateway to come back up
+            sleep 5
 
-            cd "$DEPLOY_DIR"
-            git fetch origin
-            git checkout -- .
-            git clean -fd
-            git checkout "$BRANCH"
-            git reset --hard "origin/$BRANCH"
+            # Health check: verify the LogLife plugin is loaded and responding
+            SESSIONS_STATUS=$(curl -sf -o /dev/null -w "%{http_code}" \
+              -H "Authorization: Bearer $LOGLIFE_API_KEY" \
+              "http://localhost:18789/loglife/sessions?phone=healthcheck" || echo "000")
 
-            cd website
-            pnpm install --frozen-lockfile
-            pnpm run build
+            VERIFY_STATUS=$(curl -sf -o /dev/null -w "%{http_code}" \
+              -X POST -H "Authorization: Bearer $LOGLIFE_API_KEY" \
+              -H "Content-Type: application/json" \
+              -d '{"phone":"0","code":"000000"}' \
+              "http://localhost:18789/loglife/verify/check" || echo "000")
 
-            NODE_BIN=$(which node)
-            NEXT_BIN="$DEPLOY_DIR/website/node_modules/.bin/next"
+            echo "Plugin health check: sessions=$SESSIONS_STATUS verify=$VERIFY_STATUS"
 
-            mkdir -p "$HOME/.config/systemd/user"
-            printf '%s\n' \
-              "[Unit]" \
-              "Description=LogLife Preview" \
-              "After=network.target" \
-              "" \
-              "[Service]" \
-              "Type=simple" \
-              "WorkingDirectory=$DEPLOY_DIR/website" \
-              "Environment=PORT=$PORT" \
-              "Environment=NODE_ENV=production" \
-              "Environment=NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY=$NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY" \
-              "ExecStart=$NODE_BIN $NEXT_BIN start --port $PORT" \
-              "Restart=on-failure" \
-              "" \
-              "[Install]" \
-              "WantedBy=default.target" \
-              > "$HOME/.config/systemd/user/$APP_NAME.service"
+            # 404 = plugin loaded, searched, found nothing (expected)
+            # 200 = plugin loaded, returned data (also fine)
+            if [ "$SESSIONS_STATUS" != "404" ] && [ "$SESSIONS_STATUS" != "200" ]; then
+              echo "ERROR: Sessions endpoint returned unexpected status $SESSIONS_STATUS"
+              exit 1
+            fi
+
+            # 200 = plugin loaded, returned {verified:false} (expected)
+            if [ "$VERIFY_STATUS" != "200" ]; then
+              echo "ERROR: Verify endpoint returned unexpected status $VERIFY_STATUS"
+              exit 1
+            fi
 
-            systemctl --user daemon-reload
-            systemctl --user enable "$APP_NAME"
-            systemctl --user restart "$APP_NAME"
+            echo "All health checks passed."

README.md

@@ -39,33 +39,87 @@ It combines a minimalist interface with powerful AI processing to help you **Cap
 ## 🏁 Getting Started
 
 ### Prerequisites
-*   Node.js 24+
-*   pnpm
-
-### Running the Website
-
-1.  **Clone the repository:**
-    ```bash
-    git clone https://github.com/jmoraispk/loglife.git
-    cd loglife/website
-    ```
-
-2.  **Install dependencies:**
-    ```bash
-    pnpm install
-    ```
-
-3.  **Run the development server:**
-    ```bash
-    pnpm dev
-    ```
-    *The site will be available at `http://localhost:3000`.*
-
-4.  **Build for production:**
-    ```bash
-    pnpm build
-    pnpm start
-    ```
+
+- Node.js 24+
+- pnpm 10+
+- [OpenClaw](https://github.com/openclaw/openclaw) (for the dashboard)
+
+### Full development setup
+
+#### 1. Clone the repos
+
+```bash
+git clone https://github.com/jmoraispk/loglife.git
+git clone https://github.com/openclaw/openclaw.git ~/openclaw
+```
+
+#### 2. Build OpenClaw and install the plugin
+
+```bash
+cd ~/openclaw
+pnpm install
+pnpm build
+./openclaw.mjs plugins install /path/to/loglife/plugin --link
+./openclaw.mjs config set plugins.entries.loglife.config.apiKey "$(openssl rand -hex 32)"
+```
+
+#### 3. Start the OpenClaw gateway
+
+```bash
+cd ~/openclaw
+./openclaw.mjs gateway --allow-unconfigured
+```
+
+#### 4. Set up and run the website
+
+```bash
+cd loglife/website
+pnpm install
+```
+
+Copy `.env` and add your OpenClaw connection:
+
+```
+OPENCLAW_API_URL=http://localhost:18789
+OPENCLAW_API_KEY=<your key from step 2>
+```
+
+```bash
+pnpm dev
+```
+
+The site will be available at `http://localhost:3000`. The dashboard connects to the OpenClaw gateway to display session data.
+
+### Website only (no dashboard)
+
+If you only need the marketing site without the dashboard:
+
+```bash
+cd loglife/website
+pnpm install
+pnpm dev
+```
+
+### Production build
+
+```bash
+cd loglife/website
+pnpm build
+pnpm start
+```
+
+### Architecture
+
+```
+loglife/
+├── website/     → Next.js app (Vercel) — marketing site + dashboard
+├── plugin/      → OpenClaw plugin — serves session data over HTTP
+├── docs/        → Mintlify documentation (docs.loglife.co)
+├── multi-user/  → Multi-user infrastructure for OpenClaw
+└── call_prompts/→ Voice call prompt templates
+```
+
+The website is hosted on Vercel. The plugin runs inside the OpenClaw gateway on your server. The dashboard proxies requests through Vercel to the plugin, keeping the server URL and API key private. See [`plugin/README.md`](plugin/README.md) for detailed setup and CI/CD instructions.
 
 ---