personal-projects/gitea-mcp-remote
1
0
Fork 0
generated from personal-projects/leo-claude-mktplace
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

[Sprint 02] infra: Create Docker deployment infrastructure #15

New Issue
Closed
opened 2026-02-03 21:01:56 +00:00 by lmiranda · 1 comment
lmiranda commented 2026-02-03 21:01:56 +00:00
Owner
Copy Link

Summary

Create Docker and Caddy infrastructure for deploying the wrapper as a containerized service.

Tasks

Dockerfile

  • Create docker/Dockerfile
  • Base image: python:3.11-slim
  • Install dependencies from pyproject.toml
  • Copy src/gitea_mcp_remote/ into container
  • Set working directory
  • Expose port 8000
  • CMD: python -m gitea_mcp_remote.server_http

Docker Compose

  • Create docker/docker-compose.yml
  • Define gitea-mcp-remote service
  • Mount .env file for configuration
  • Expose port 8000 to localhost only (not 0.0.0.0)
  • Set restart policy: unless-stopped
  • Configure logging driver
  • Add healthcheck endpoint

Caddyfile

  • Create docker/Caddyfile
  • Configure reverse proxy to container:8000
  • Set up subdomain: gitea-mcp.hotserv.cloud
  • Enable automatic HTTPS
  • Add request logging
  • Configure CORS headers for MCP client access

Acceptance Criteria

  • docker/Dockerfile builds successfully
  • docker/docker-compose.yml starts container
  • docker/Caddyfile proxies requests correctly
  • Container can be built: docker build -t gitea-mcp-remote -f docker/Dockerfile .
  • Container can be started: docker compose -f docker/docker-compose.yml up -d
  • Service accessible at configured subdomain
  • Logs visible via docker compose logs -f

Dependencies

Blocked by: #14 (server must exist to containerize)

Context

Docker + Caddy provides production-ready deployment. The wrapper runs in a container behind Caddy reverse proxy with automatic HTTPS.

References:

  • Corrective Rebuild specification
  • Steps 8-10 of 14-step rebuild plan

Size: M (3-4 hours)

## Summary Create Docker and Caddy infrastructure for deploying the wrapper as a containerized service. ## Tasks ### Dockerfile - [ ] Create `docker/Dockerfile` - [ ] Base image: `python:3.11-slim` - [ ] Install dependencies from `pyproject.toml` - [ ] Copy `src/gitea_mcp_remote/` into container - [ ] Set working directory - [ ] Expose port 8000 - [ ] CMD: `python -m gitea_mcp_remote.server_http` ### Docker Compose - [ ] Create `docker/docker-compose.yml` - [ ] Define `gitea-mcp-remote` service - [ ] Mount `.env` file for configuration - [ ] Expose port 8000 to localhost only (not 0.0.0.0) - [ ] Set restart policy: `unless-stopped` - [ ] Configure logging driver - [ ] Add healthcheck endpoint ### Caddyfile - [ ] Create `docker/Caddyfile` - [ ] Configure reverse proxy to container:8000 - [ ] Set up subdomain: `gitea-mcp.hotserv.cloud` - [ ] Enable automatic HTTPS - [ ] Add request logging - [ ] Configure CORS headers for MCP client access ## Acceptance Criteria - `docker/Dockerfile` builds successfully - `docker/docker-compose.yml` starts container - `docker/Caddyfile` proxies requests correctly - Container can be built: `docker build -t gitea-mcp-remote -f docker/Dockerfile .` - Container can be started: `docker compose -f docker/docker-compose.yml up -d` - Service accessible at configured subdomain - Logs visible via `docker compose logs -f` ## Dependencies **Blocked by:** #14 (server must exist to containerize) ## Context Docker + Caddy provides production-ready deployment. The wrapper runs in a container behind Caddy reverse proxy with automatic HTTPS. **References:** - Corrective Rebuild specification - Steps 8-10 of 14-step rebuild plan **Size:** M (3-4 hours)
lmiranda added this to the Sprint 02: Corrective Rebuild milestone 2026-02-03 21:01:56 +00:00
lmiranda commented 2026-02-03 21:02:00 +00:00
Author
Owner
Copy Link

⚠️ Blocked By: #14

⚠️ **Blocked By:** #14
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Component/API
API endpoints, contracts, and integration
 Component/Auth
Authentication and authorization
 Component/Backend
Backend/server-side code
 Component/Backend
Backend service code and business logic
 Component/Core
Core application logic and architecture
 Component/Database
Database schemas, migrations, queries
 Component/Dependencies
Package dependencies and requirements
 Component/Deploy
Deployment, infrastructure, DevOps
 Component/Docker
Docker and containerization
 Component/Docs
Documentation and guides
 Component/Documentation
Documentation and guides
 Component/Frontend
User interface and client-side code
 Component/Infra
Infrastructure and system configuration
 Component/Integration
Integration and end-to-end testing
 Component/Testing
Test infrastructure and frameworks
 Priority/Critical
Critical priority - blocks other work
 Priority/High
High priority items
 Priority/Medium
Medium priority items
 Size/L
Large task (4-8 hours)
 Size/M
Medium task (2-4 hours)
 Size/S
Small task (1-2 hours)
 Tech/Docker
Docker containers and compose
 Tech/FastAPI
FastAPI backend framework
 Tech/JavaScript
JavaScript/Node.js code
 Tech/PostgreSQL
PostgreSQL database
 Tech/Python
Python language and libraries
 Tech/Redis
Redis cache and pub/sub
 Tech/Vue
Vue.js frontend framework
 Type/Build
Build system and dependencies
 Type/Documentation
Documentation updates
 Type/Feature
New feature implementation
 Type/Refactor
Code refactoring and restructuring
 Type/Setup
Initial project setup tasks
 Type/Test
Testing and quality assurance
Complexity/Complex
High uncertainty or many dependencies
 Complexity/Medium
Some unknowns or dependencies
 Complexity/Simple
Straightforward, well-understood
 Effort/L
3-5 days
 Effort/M
1-2 days
 Effort/S
2-4 hours
 Effort/XL
> 1 week
 Effort/XS
< 2 hours
 Priority/Critical
Immediate attention required
 Priority/High
Important, needs attention soon
 Priority/Low
Nice to have, can wait
 Priority/Medium
Normal priority
 Type/Bug
Something isn't working
 Type/Chore
Maintenance tasks
 Type/Documentation
Documentation improvements
 Type/Feature
New feature or request
 Type/Refactor
Code refactoring without changing behavior
 Type/Test
Testing related
No Label Component/Deploy Component/Infra Priority/High Size/M Tech/Docker Type/Feature
Milestone
No items
No Milestone Sprint 02: Corrective Rebuild
Projects
Clear projects
No project
Assignees
Clear assignees
lmiranda
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: personal-projects/gitea-mcp-remote#15
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?