# Vibe Kanban Project Settings Configuration

## Settings URL
http://127.0.0.1:63100/settings/projects?projectId=1a4fdbff-8b23-49d5-9953-2476846cbcc2

## Configuration Steps

### 1. MCP Servers Configuration

In the **MCP Servers** section, add or verify:

**Server Name:** `dev-manager`

**Configuration:**
```json
{
  "command": "npx",
  "args": ["dev-manager-mcp", "stdio"]
}
```

This enables Vibe Kanban to use dev-manager-mcp for managing multiple dev server instances.

### 2. QA / Testing Configuration

In the **QA** or **Testing** section, configure:

**Enable QA Automation:** ✅ Checked

**Dev Environment Script:**
```
managing-apps/scripts/vibe-kanban/vibe-dev-server.sh
```

**Or use absolute path:**
```
/Users/oda/Desktop/Projects/managing-apps/scripts/vibe-kanban/vibe-dev-server.sh
```

**Note:** This path is relative to `/Users/oda/Desktop/Projects` (the Projects folder root)

**Health Check URL:**
```
http://localhost:{port}/health
```

**Dashboard URL (optional):**
```
http://localhost:{port}
```

### 3. Task Status Configuration

Configure which task statuses should auto-start dev environments:

**Status:** `ready-for-qa`

**Auto-start dev environment:** ✅ Enabled

This means when a task moves to "Ready for QA" status, Vibe Kanban will automatically:
1. Call `managing-apps/scripts/start-task-docker.sh` with the task ID
2. Wait for the environment to be ready
3. Provide the test URLs
4. Stop the environment when the task is completed

### 4. Project Root

**Project Root Path:**
```
/Users/oda/Desktop/Projects/managing-apps
```

This should be automatically detected from the `.vibe-kanban/config.json` file location.

## Complete Configuration Summary

Here's what should be configured:

### MCP Servers
- ✅ `dev-manager` → `npx dev-manager-mcp stdio`

### QA Settings
- ✅ Auto-start dev environments: **Enabled**
- ✅ Script: `managing-apps/scripts/start-task-docker.sh`
- ✅ Health check: `http://localhost:{port}/health`
- ✅ Dashboard: `http://localhost:{port}`

### Task Statuses
- ✅ `ready-for-qa` → Auto-start dev environment: **Enabled**

## Verification

After configuration, test by:

1. **Create a test task** in managing-apps project
2. **Move it to "Ready for QA"** status
3. **Verify** that Vibe Kanban automatically:
   - Starts a Docker environment
   - Copies the database
   - Provides test URLs
   - Shows the environment status

## Troubleshooting

### Script Not Found
- Verify the script path is relative to Projects folder: `managing-apps/scripts/start-task-docker.sh`
- Check that the script is executable: `chmod +x managing-apps/scripts/start-task-docker.sh`

### MCP Server Not Working
- Ensure dev-manager-mcp daemon is running: `npm run dev-manager:start` (in Projects folder)
- Check MCP server configuration matches exactly

### Environment Not Starting
- Check Docker is running
- Verify main database is accessible at localhost:5432
- Check script logs in Vibe Kanban

## Script Path Reference

Since Vibe Kanban runs from `/Users/oda/Desktop/Projects`, all script paths should be relative to that:

- ✅ `managing-apps/scripts/start-task-docker.sh`
- ✅ `managing-apps/scripts/stop-task-docker.sh`
- ✅ `managing-apps/scripts/copy-database-for-task.sh`

