e2e fixin, frontend + home page work

2026-01-21 14:39:21 -08:00
parent 6e13570deb
commit 8bd4e081ea
18 changed files with 191 additions and 79 deletions
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -424,11 +424,24 @@ psql -d "flyer-crawler-test" -c "\dn+ public"

 The dev container runs its own **local Bugsink instance** - it does NOT connect to the production Bugsink server:

- **Local Bugsink**: Runs at `http://localhost:8000` inside the container
- **Pre-configured DSNs**: Set in `compose.dev.yml`, pointing to local instance
+- **Local Bugsink UI**: Accessible at `https://localhost:8443` (proxied from `http://localhost:8000` by nginx)
 - **Admin credentials**: `admin@localhost` / `admin`
+- **Bugsink Projects**: Backend (Dev) - Project ID 1, Frontend (Dev) - Project ID 2
+- **Configuration Files**:
+  - `compose.dev.yml` - Sets default DSNs using `127.0.0.1:8000` protocol (for initial container setup)
+  - `.env.local` - **OVERRIDES** compose.dev.yml with `localhost:8000` protocol (this is what the app actually uses)
+  - **CRITICAL**: `.env.local` takes precedence over `compose.dev.yml` environment variables
+- **DSN Configuration**:
+  - **Backend DSN** (Node.js/Express): Configured in `.env.local` as `SENTRY_DSN=http://<key>@localhost:8000/1`
+  - **Frontend DSN** (React/Browser): Configured in `.env.local` as `VITE_SENTRY_DSN=http://<key>@localhost:8000/2`
+  - **Why localhost instead of 127.0.0.1?** The `.env.local` file was created separately and uses `localhost` which works fine in practice
+- **HTTPS Setup**: Self-signed certificates auto-generated with mkcert on container startup (for UI access only, not for Sentry SDK)
+- **CSRF Protection**: Django configured with `SECURE_PROXY_SSL_HEADER` to trust `X-Forwarded-Proto` from nginx
 - **Isolated**: Dev errors stay local, don't pollute production/test dashboards
 - **No Gitea secrets needed**: Everything is self-contained in the container
+- **Accessing Errors**:
+  - **Via Browser**: Open `https://localhost:8443` and login to view issues
+  - **Via MCP**: Configure a second Bugsink MCP server pointing to `http://localhost:8000` (see MCP Servers section below)

 ---

@@ -436,64 +449,105 @@ The dev container runs its own **local Bugsink instance** - it does NOT connect

 The following MCP servers are configured for this project:

-| Server                | Purpose                                     |
-| --------------------- | ------------------------------------------- |
-| gitea-projectium      | Gitea API for gitea.projectium.com          |
-| gitea-torbonium       | Gitea API for gitea.torbonium.com           |
-| podman                | Container management                        |
-| filesystem            | File system access                          |
-| fetch                 | Web fetching                                |
-| markitdown            | Convert documents to markdown               |
-| sequential-thinking   | Step-by-step reasoning                      |
-| memory                | Knowledge graph persistence                 |
-| postgres              | Direct database queries (localhost:5432)    |
-| playwright            | Browser automation and testing              |
-| redis                 | Redis cache inspection (localhost:6379)     |
-| sentry-selfhosted-mcp | Error tracking via Bugsink (localhost:8000) |
+| Server              | Purpose                                                                      |
+| ------------------- | ---------------------------------------------------------------------------- |
+| gitea-projectium    | Gitea API for gitea.projectium.com                                           |
+| gitea-torbonium     | Gitea API for gitea.torbonium.com                                            |
+| podman              | Container management                                                         |
+| filesystem          | File system access                                                           |
+| fetch               | Web fetching                                                                 |
+| markitdown          | Convert documents to markdown                                                |
+| sequential-thinking | Step-by-step reasoning                                                       |
+| memory              | Knowledge graph persistence                                                  |
+| postgres            | Direct database queries (localhost:5432)                                     |
+| playwright          | Browser automation and testing                                               |
+| redis               | Redis cache inspection (localhost:6379)                                      |
+| bugsink             | Error tracking - production Bugsink (bugsink.projectium.com) - **PROD/TEST** |
+| bugsink-dev         | Error tracking - dev container Bugsink (localhost:8000) - **DEV CONTAINER**  |

 **Note:** MCP servers work in both **Claude CLI** and **Claude Code VS Code extension** (as of January 2026).

-### Sentry/Bugsink MCP Server Setup (ADR-015)
+**CRITICAL**: There are **TWO separate Bugsink MCP servers**:

-To enable Claude Code to query and analyze application errors from Bugsink:
+- **bugsink**: Connects to production Bugsink at `https://bugsink.projectium.com` for production and test server errors
+- **bugsink-dev**: Connects to local dev container Bugsink at `http://localhost:8000` for local development errors

-1. **Install the MCP server**:
+### Bugsink MCP Server Setup (ADR-015)

-   ```bash
-   # Clone the sentry-selfhosted-mcp repository
-   git clone https://github.com/ddfourtwo/sentry-selfhosted-mcp.git
-   cd sentry-selfhosted-mcp
-   npm install
-   ```
+**IMPORTANT**: You need to configure **TWO separate MCP servers** - one for production/test, one for local dev.

-2. **Configure Claude Code** (add to `.claude/mcp.json`):
+#### Installation (shared for both servers)

-   ```json
-   {
-     "sentry-selfhosted-mcp": {
-       "command": "node",
-       "args": ["/path/to/sentry-selfhosted-mcp/dist/index.js"],
-       "env": {
-         "SENTRY_URL": "http://localhost:8000",
-         "SENTRY_AUTH_TOKEN": "<get-from-bugsink-ui>",
-         "SENTRY_ORG_SLUG": "flyer-crawler"
-       }
-     }
-   }
-   ```
+```bash
+# Clone the bugsink-mcp repository (NOT sentry-selfhosted-mcp)
+git clone https://github.com/j-shelfwood/bugsink-mcp.git
+cd bugsink-mcp
+npm install
+npm run build
+```

-3. **Get the auth token**:
-   - Navigate to Bugsink UI at `http://localhost:8000`
-   - Log in with admin credentials
-   - Go to Settings > API Keys
-   - Create a new API key with read access
+#### Production/Test Bugsink MCP (bugsink)

-4. **Available capabilities**:
-   - List projects and issues
-   - View detailed error events
-   - Search by error message or stack trace
-   - Update issue status (resolve, ignore)
-   - Add comments to issues
+Add to `.claude/mcp.json`:
+
+```json
+{
+  "bugsink": {
+    "command": "node",
+    "args": ["d:\\gitea\\bugsink-mcp\\dist\\index.js"],
+    "env": {
+      "BUGSINK_URL": "https://bugsink.projectium.com",
+      "BUGSINK_API_TOKEN": "<get-from-production-bugsink>",
+      "BUGSINK_ORG_SLUG": "sentry"
+    }
+  }
+}
+```
+
+**Get the auth token**:
+
+- Navigate to https://bugsink.projectium.com
+- Log in with production credentials
+- Go to Settings > API Keys
+- Create a new API key with read access
+
+#### Dev Container Bugsink MCP (bugsink-dev)
+
+Add to `.claude/mcp.json`:
+
+```json
+{
+  "bugsink-dev": {
+    "command": "node",
+    "args": ["d:\\gitea\\bugsink-mcp\\dist\\index.js"],
+    "env": {
+      "BUGSINK_URL": "http://localhost:8000",
+      "BUGSINK_API_TOKEN": "<get-from-local-bugsink>",
+      "BUGSINK_ORG_SLUG": "sentry"
+    }
+  }
+}
+```
+
+**Get the auth token**:
+
+- Navigate to http://localhost:8000 (or https://localhost:8443)
+- Log in with `admin@localhost` / `admin`
+- Go to Settings > API Keys
+- Create a new API key with read access
+
+#### MCP Tool Usage
+
+When using Bugsink MCP tools, remember:
+
+- `mcp__bugsink__*` tools connect to **production/test** Bugsink
+- `mcp__bugsink-dev__*` tools connect to **dev container** Bugsink
+- Available capabilities for both:
+  - List projects and issues
+  - View detailed error events and stacktraces
+  - Search by error message or stack trace
+  - Update issue status (resolve, ignore)
+  - Create releases

 ### SSH Server Access