[Infra] Docker Compose — Full Stack Single-Command Dev Environment #875

Closed
opened 2026-03-21 23:40:06 +00:00 by perplexity · 0 comments
Collaborator

Why This Is High Leverage

The Phase 9 open-source release requires git clone && docker-compose up to get users running in under 10 minutes. But more immediately, this unblocks Timmy, Kimi, Replit, and Perplexity from needing manual setup to contribute. Every developer friction point is a multiplier on wasted time.

Scope

Create a Docker Compose configuration that brings up the entire Timmy Time stack:

Services

  • timmy — The agent (FastAPI + agentic loop + Ollama client)
  • ollama — Local LLM inference (Hermes 3 8B for dev, 70B for production)
  • dashboard — Web dashboard
  • redis — Inter-agent communication (Phase 8 prerequisite)
  • nginx — Reverse proxy + optional RTMP streaming

Developer Experience

  • make dev — start everything
  • make test — run all tests
  • make test-agents — run agent-specific tests
  • Health checks on all services
  • Volume mounts for live code reload
  • .env.example with every configuration variable documented

Requirements

  • docker-compose.yml — All services defined with health checks
  • docker-compose.dev.yml — Override for local development (volume mounts, debug ports)
  • Dockerfile — Multi-stage build for the Python application
  • Makefile — Developer-facing targets
  • .env.example — Every env var documented
  • docs/quickstart.md — Clone-to-running in under 10 minutes
  • .devcontainer/ — GitHub Codespaces support (LangChain pattern)

Acceptance Criteria

  • docker-compose up starts all services, health checks pass within 60 seconds
  • A new developer can go from git clone to working environment in <10 minutes
  • Tests run in Docker without host dependencies

Assignee: Kimi

## Why This Is High Leverage The Phase 9 open-source release requires `git clone && docker-compose up` to get users running in under 10 minutes. But more immediately, this unblocks Timmy, Kimi, Replit, and Perplexity from needing manual setup to contribute. Every developer friction point is a multiplier on wasted time. ## Scope Create a Docker Compose configuration that brings up the entire Timmy Time stack: ### Services - `timmy` — The agent (FastAPI + agentic loop + Ollama client) - `ollama` — Local LLM inference (Hermes 3 8B for dev, 70B for production) - `dashboard` — Web dashboard - `redis` — Inter-agent communication (Phase 8 prerequisite) - `nginx` — Reverse proxy + optional RTMP streaming ### Developer Experience - `make dev` — start everything - `make test` — run all tests - `make test-agents` — run agent-specific tests - Health checks on all services - Volume mounts for live code reload - `.env.example` with every configuration variable documented ## Requirements - [ ] `docker-compose.yml` — All services defined with health checks - [ ] `docker-compose.dev.yml` — Override for local development (volume mounts, debug ports) - [ ] `Dockerfile` — Multi-stage build for the Python application - [ ] `Makefile` — Developer-facing targets - [ ] `.env.example` — Every env var documented - [ ] `docs/quickstart.md` — Clone-to-running in under 10 minutes - [ ] `.devcontainer/` — GitHub Codespaces support (LangChain pattern) ## Acceptance Criteria - `docker-compose up` starts all services, health checks pass within 60 seconds - A new developer can go from git clone to working environment in <10 minutes - Tests run in Docker without host dependencies ## Assignee: Kimi
gemini was assigned by Rockachopa 2026-03-22 23:33:30 +00:00
gemini was unassigned by Timmy 2026-03-24 19:33:56 +00:00
Timmy closed this issue 2026-03-24 21:54:50 +00:00
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#875