Merge pull request #1254 from Mentra-Community/dev

Dev

Author: aisraelov

.github/CODEOWNERS

@@ -0,0 +1 @@
+* @Mentra-Community/core

.github/scripts/clean-runner.sh

@@ -0,0 +1,33 @@
+#!/bin/bash
+# Script to clean up self-hosted runner environment
+
+echo "Cleaning up self-hosted runner environment..."
+
+# Clean up pnpm caches and stores
+echo "Cleaning pnpm caches..."
+rm -rf ~/.pnpm-store
+rm -rf ~/.cache/pnpm
+rm -rf ~/.local/share/pnpm
+rm -rf ~/.pnpm
+
+# Clean up work directories
+echo "Cleaning work directories..."
+for dir in /home/*/actions-runner*/_work/*/; do
+  if [ -d "$dir" ]; then
+    echo "Cleaning $dir"
+    find "$dir" -name "node_modules" -type d -prune -exec rm -rf {} +
+    find "$dir" -name ".pnpm-store" -type d -prune -exec rm -rf {} +
+    find "$dir" -name ".pnpm" -type d -prune -exec rm -rf {} +
+  fi
+done
+
+# Clean up npm/yarn caches (in case they're used)
+echo "Cleaning npm/yarn caches..."
+npm cache clean --force 2>/dev/null || true
+yarn cache clean 2>/dev/null || true
+
+# Clean up gradle caches
+echo "Cleaning gradle caches..."
+rm -rf ~/.gradle/caches/*
+
+echo "Cleanup complete!"

.github/self-hosted-runner-guide.md

@@ -0,0 +1,94 @@
+# Self-Hosted Runner Guide for MentraOS
+
+## Overview
+
+This guide helps you set up and maintain self-hosted GitHub Actions runners for MentraOS builds.
+
+## Key Issues and Solutions
+
+### 1. PNPM Store Permission Issues
+
+**Problem**: `ERR_PNPM_ENOENT` errors when pnpm tries to use global store paths.
+
+**Solution**: Configure pnpm to use project-local stores:
+
+```yaml
+- name: Configure pnpm store
+  working-directory: ./mobile
+  run: |
+    pnpm config set store-dir .pnpm-store
+
+- name: Install dependencies
+  working-directory: ./mobile
+  run: pnpm install --no-frozen-lockfile
+  env:
+    PNPM_HOME: ${{ github.workspace }}/mobile/.pnpm
+    PNPM_STORE_PATH: ${{ github.workspace }}/mobile/.pnpm-store
+```
+
+### 2. Runner Cleanup
+
+Self-hosted runners persist state between runs. Clean workspaces regularly:
+
+```bash
+# Run on the self-hosted runner VM
+chmod +x .github/scripts/clean-runner.sh
+.github/scripts/clean-runner.sh
+```
+
+### 3. Concurrent Jobs
+
+By default, one runner = one job at a time. For parallel builds:
+
+```bash
+# Install multiple runners on same VM
+cd ~
+for i in {1..3}; do
+  mkdir actions-runner-$i && cd actions-runner-$i
+  curl -o actions-runner-linux-x64-2.326.0.tar.gz -L [runner-url]
+  tar xzf actions-runner-linux-x64-2.326.0.tar.gz
+  ./config.sh --url https://github.com/Mentra-Community/MentraOS --token [TOKEN] --name "runner-$i"
+  sudo ./svc.sh install
+  sudo ./svc.sh start
+  cd ..
+done
+```
+
+### 4. Best Practices
+
+1. **Use local stores**: Avoid global pnpm/npm stores
+2. **Clean workspaces**: Remove build artifacts between runs
+3. **Monitor disk space**: Android builds use lots of space
+4. **Label runners**: Use labels like `android`, `heavy-build`
+5. **Fallback strategy**: Keep some jobs on GitHub-hosted runners
+
+### 5. Recommended VM Specs
+
+- **For Android builds**: 8+ vCPUs, 32GB RAM (D8as_v5 on Azure)
+- **Concurrent builds**: 16 vCPUs, 64GB RAM (D16as_v5)
+- **Disk**: 256GB+ SSD
+
+### 6. Monitoring
+
+```bash
+# Check runner status
+sudo systemctl status 'actions.runner.*.service'
+
+# View logs
+journalctl -u actions.runner.Mentra-Community-MentraOS.* -f
+
+# Check disk usage
+df -h
+
+# Monitor CPU/RAM
+htop
+```
+
+### 7. Emergency Fixes
+
+If builds are failing:
+
+1. SSH into runner VM
+2. Run cleanup script: `.github/scripts/clean-runner.sh`
+3. Restart runner services: `sudo systemctl restart 'actions.runner.*.service'`
+4. Check GitHub Actions runner page for connection status

.github/workflows/augmentos-manager-jest.yml

@@ -0,0 +1,45 @@
+name: Mobile App Jest Tests
+
+on:
+  pull_request:
+    paths:
+      - "mobile/**"
+      - ".github/workflows/augmentos-manager-jest.yml"
+  workflow_dispatch:
+
+jobs:
+  test:
+    runs-on: self-hosted
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: "18"
+
+      - name: Install pnpm
+        run: |
+          npm install -g pnpm@8
+          pnpm --version
+
+      - name: Configure pnpm store
+        working-directory: ./mobile
+        run: |
+          # Use local store to avoid permission issues
+          pnpm config set store-dir .pnpm-store
+
+      - name: Install dependencies
+        working-directory: ./mobile
+        run: pnpm install --no-frozen-lockfile
+        env:
+          PNPM_HOME: ${{ github.workspace }}/mobile/.pnpm
+          PNPM_STORE_PATH: ${{ github.workspace }}/mobile/.pnpm-store
+
+      - name: Run Jest tests
+        working-directory: ./mobile
+        run: pnpm test
+        env:
+          CI: true

.github/workflows/augmentos_cloud.yml

@@ -1,15 +1,13 @@
 # Name of the workflow
-name: Deploy AugmentOS Cloud ☁️ Dev environment
+name: Test AugmentOS Cloud ☁️
 
-# Trigger on pushes to isaiah/cloud branch
+# trigger
 on:
   push:
-    branches: [ "isaiah/cloud" ]
-    # Optionally, filter paths if you only want to deploy on changes to augmentos_cloud
-    # paths:
-    #   - 'augmentos_cloud/**'
+    paths:
+      - "cloud/**"
+      - ".github/workflows/cloud.yml"
 
-# We use two jobs: build and deploy, for modularity and future scalability
 jobs:
   build_and_test:
     name: Build & Test
@@ -18,7 +16,7 @@ jobs:
       # (Optional) Specify Node environment, could also set BUN_ENV if needed.
       NODE_ENV: development
       # If Bun version is to be pinned, we can specify it here.
-      BUN_VERSION:  # e.g. "1.2.0" or leave blank for latest
+      BUN_VERSION: # e.g. "1.2.0" or leave blank for latest
     steps:
       # 1. Checkout the repository
       - name: Checkout code
@@ -32,7 +30,7 @@ jobs:
         uses: oven-sh/setup-bun@v2
         with:
           bun-version: ${{ env.BUN_VERSION || 'latest' }}
-      # ^ This installs Bun on the runner, allowing us to use the `bun` command​:contentReference[oaicite:15]{index=15}.
+      # ^ This installs Bun on the runner, allowing us to use the `bun` command
 
       # 3. Restore cached dependencies to speed up build if possible
       - name: Cache Bun dependencies
@@ -41,37 +39,41 @@ jobs:
           # Path to Bun's global package cache on the runner
           path: ~/.bun/install/cache
           # Key includes OS and lockfile hash. If bun.lockb (lockfile) hasn't changed, cache hits.
-          key: ${{ runner.os }}-bun-${{ hashFiles('augmentos_cloud/bun.lockb') }}
+          key: ${{ runner.os }}-bun-${{ hashFiles('cloud/bun.lockb') }}
           # In case of partial match, allow restore with just OS identifier (fallback).
           restore-keys: |
             ${{ runner.os }}-bun-
-      # ^ Uses GitHub cache to store Bun's package cache for faster installs​:contentReference[oaicite:16]{index=16}.
-
-      # 4. Install project dependencies using Bun
+      # ^ Uses GitHub cache to store Bun's package cache for faster installs
       - name: Install Dependencies
-        working-directory: augmentos_cloud
-        run: bun install
+        working-directory: cloud
+        run: bun run setup-deps
+
+      # 3. build other projects
+      - name: Build all projects
+        working-directory: cloud
+        run: bun run build
+
       # ^ Installs NPM packages. Bun uses its lockfile to ensure deterministic installs.
       # If cache was restored, this will be fast as packages are already downloaded.
 
       # 5. Run linter to ensure code quality
-      - name: Lint code
-        working-directory: augmentos_cloud
-        run: bun run lint
+      #- name: Lint code
+      #  working-directory: cloud
+      #  run: bun run lint
       # ^ Runs the lint script (assumes package.json has a "lint" script or use bunx directly for ESLint).
       # Linting is done before tests to fail fast on syntax/style issues​:contentReference[oaicite:17]{index=17}.
 
       # 6. Run tests to verify functionality
       - name: Run tests
-        working-directory: augmentos_cloud
+        working-directory: cloud/packages/cloud
         run: bun run test
       # ^ Executes the test suite (e.g., via Jest, Bun's built-in test runner, or another framework).
       # If any tests fail, the job (and workflow) will fail, preventing deployment.
 
       # 7. (Optional) Build step for production
-      - name: Build project
-        working-directory: augmentos_cloud
-        run: bun run build
+      #- name: Build project
+      #  working-directory: cloud
+      #  run: bun run build
       # ^ If the server requires a build (e.g., TypeScript compilation or bundling), do it here.
       # If not needed, this step can be removed or left as a no-op.
 
@@ -80,72 +82,4 @@ jobs:
       #   uses: actions/upload-artifact@v3
       #   with:
       #     name: augmentos_build
-      #     path: augmentos_cloud/**
-
-  deploy:
-    name: Deploy to Azure VM
-    needs: build_and_test   # Only run if build_and_test job succeeded
-    runs-on: ubuntu-latest
-    # We don't set env here to avoid exposing secrets via env. We'll pass secrets directly.
-    steps:
-      # 1. (Optional) Checkout code again, if we need the files in this job
-      - name: Checkout code
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 1
-          # We could also use the artifact from previous job instead of checking out again.
-          # In a monorepo, checkout ensures we have the latest from main for this job.
-
-      # 2. Copy files to Azure VM via SCP (Secure Copy over SSH)
-      - name: Copy files to VM
-        uses: appleboy/[email protected]
-        with:
-          host: ${{ secrets.AZURE_HOST }}         # Azure VM IP or hostname
-          username: ${{ secrets.AZURE_USERNAME }} # SSH username on Azure VM
-          key: ${{ secrets.AZURE_DEV_RSA_KEY}}       # Private SSH key for the VM (from secrets)
-          port: 22                                # SSH port (default 22)
-          source: "augmentos_cloud/*"             # What to copy (all files in server folder)
-          target: "~/augmentos_cloud/"            # Where to copy on the VM (adjust path as needed)
-          rm: "true"
-      # ^ This uses a community action to securely copy the latest build files to the VM​:contentReference[oaicite:18]{index=18}.
-      # It removes existing files in target (rm: true) to ensure old files are cleaned up.
-      # Ensure the target directory exists on the VM. You might want to exclude certain files (like .env).
-
-      # 3. Run remote commands on the VM via SSH
-      - name: Install and Restart Server on VM
-        uses: appleboy/[email protected]
-        with:
-          host: ${{ secrets.AZURE_HOST }}
-          username: ${{ secrets.AZURE_USERNAME }}
-          key: ${{ secrets.AZURE_DEV_RSA_KEY }}
-          script: |
-            set -e  # stop on error
-            cd ~/augmentos_cloud/
-            # Install production dependencies on VM (if needed, e.g., in case node_modules was not copied)
-            bun install --production
-            # (If using a package manager other than bun for install on VM, adjust accordingly, e.g., npm ci --only=production)
-            # Restart the Bun server process
-            # If managed by PM2:
-            pm2 restart augmentos-cloud || pm2 start index.js --name augmentos-cloud
-            # If managed by systemd:
-            # sudo systemctl restart augmentos.service
-            # If no manager (not recommended for prod), run in background:
-            # pkill -f \"bun run start\" || true   # ignore if not running
-            # nohup bun run start &>/dev/null &
-      # ^ Logs into the VM via SSH and runs the commands​:contentReference[oaicite:19]{index=19}:
-      # - Navigates to the app directory on the VM.
-      # - Installs dependencies (using bun) in production mode.
-      # - Restarts the application. (The example shows placeholders for PM2 or systemd; adapt to your setup.)
-      # Ensure your VM user has permission to restart the service (if using sudo, the user must be in sudoers).
-      # The bun server will be back up and running with the new code after this step.
-
-      # 4. (Optional) Post-deployment verification or notifications
-      # - name: Health check
-      #   run: curl -f http://your-app-url/health || exit 1
-      # - name: Notify Slack
-      #   uses: slackapi/[email protected]
-      #   with:
-      #     channel-id: C12345678
-      #     slack-message: "Deployed Bun server to Azure VM successfully."
-      #     slack-bot-token: ${{ secrets.SLACK_TOKEN }}
-
+      #     path: cloud/**