cardosofelipe/syndarix
1
0
Fork 0
forked from cardosofelipe/fast-next-template
Code Issues 18 Pull Requests Wiki Activity

feat(mcp): Git Operations MCP - Workspace Management #107

New Issue
Open
opened 2026-01-06 19:19:03 +00:00 by cardosofelipe · 0 comments
cardosofelipe commented 2026-01-06 19:19:03 +00:00
Owner
Copy Link

Parent Issue

Part of #58 (Git Operations MCP Server)

Summary

Implement workspace management for isolating git repositories per project.

Tasks

WorkspaceManager Class (workspace.py)

  • Create WorkspaceManager class
  • Define workspace base path (/var/syndarix/workspaces/)
  • Implement get_workspace(project_id) method
  • Implement create_workspace(project_id) method
  • Implement delete_workspace(project_id) method
  • Implement workspace directory structure per project
  • Add workspace cleanup for stale workspaces (>7 days unused)
  • Implement workspace locking to prevent concurrent access
  • Handle disk space monitoring
  • Add workspace size limits per project

Security

  • Validate project_id to prevent path traversal
  • Ensure workspaces are isolated
  • Implement proper file permissions

Testing

  • Unit tests for all workspace operations
  • Test concurrent access locking
  • Test cleanup of stale workspaces
  • Test path traversal prevention
  • Achieve >90% coverage

Acceptance Criteria

  • Workspaces properly isolated per project
  • No path traversal vulnerabilities
  • Concurrent access handled correctly
  • Stale workspace cleanup works
  • All tests pass

Dependencies

  • Depends on: #64 (Foundation)

Labels

  • mcp
  • phase-2
  • backend
## Parent Issue Part of #58 (Git Operations MCP Server) ## Summary Implement workspace management for isolating git repositories per project. ## Tasks ### WorkspaceManager Class (`workspace.py`) - [ ] Create `WorkspaceManager` class - [ ] Define workspace base path (`/var/syndarix/workspaces/`) - [ ] Implement `get_workspace(project_id)` method - [ ] Implement `create_workspace(project_id)` method - [ ] Implement `delete_workspace(project_id)` method - [ ] Implement workspace directory structure per project - [ ] Add workspace cleanup for stale workspaces (>7 days unused) - [ ] Implement workspace locking to prevent concurrent access - [ ] Handle disk space monitoring - [ ] Add workspace size limits per project ### Security - [ ] Validate project_id to prevent path traversal - [ ] Ensure workspaces are isolated - [ ] Implement proper file permissions ### Testing - [ ] Unit tests for all workspace operations - [ ] Test concurrent access locking - [ ] Test cleanup of stale workspaces - [ ] Test path traversal prevention - [ ] Achieve >90% coverage ## Acceptance Criteria - [ ] Workspaces properly isolated per project - [ ] No path traversal vulnerabilities - [ ] Concurrent access handled correctly - [ ] Stale workspace cleanup works - [ ] All tests pass ## Dependencies - Depends on: #64 (Foundation) ## Labels - mcp - phase-2 - backend
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
agents
Agent orchestration
 architecture
Architectural decisions
 backend
Backend work
 blocked
Blocked by dependency
 database
Database/migrations
 design
UI/UX design work
 devops
DevOps/Infrastructure work
 epic
Epic/parent issue
 frontend
Frontend work
 infrastructure
Infrastructure / DevOps
 mcp
MCP related
 phase-0
Phase 0: Foundation
 phase-1
Phase 1: Core Platform
 phase-2
Phase 2: MCP Integration
 priority:high
High priority
 spike
Architecture spike / research task
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
cardosofelipe
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: cardosofelipe/syndarix#107
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?