Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[loop-generated] [refactor] Extract config.py sections — 746 lines, monolithic configuration #1383

New Issue
Closed
opened 2026-03-24 10:48:32 +00:00 by Timmy · 2 comments
Timmy commented 2026-03-24 10:48:32 +00:00
Owner
Copy Link

Priority: Medium
Impact: Configuration maintainability, module clarity
Component: Core configuration
Size: 746 lines → target 4 focused modules

Problem

src/config.py is a 746-line monolith handling:

  • Infrastructure configuration (routers, providers)
  • Dashboard settings (Flask, UI config)
  • Timmy-specific configuration (sovereignty, tools)
  • Integration settings (Discord, Mumble, etc.)

This violates single responsibility and makes changes risky.

Proposed Split

src/config/
├── __init__.py          # Main config interface
├── infrastructure.py    # Router, provider, hermes config  
├── dashboard.py         # Flask app, UI settings
├── timmy.py            # Sovereignty, tools, core Timmy
└── integrations.py     # Discord, Mumble, chat bridges

Files Modified

  • src/config.py (746 lines → ~50 lines coordinator)
  • src/config/infrastructure.py (~200 lines)
  • src/config/dashboard.py (~150 lines)
  • src/config/timmy.py (~200 lines)
  • src/config/integrations.py (~150 lines)

Acceptance Criteria

  • All imports still work (backward compatibility)
  • No configuration values lost or changed
  • Tests pass without modification
  • Each module has single, clear responsibility
  • Import paths updated throughout codebase

Clean configuration architecture.

**Priority**: Medium **Impact**: Configuration maintainability, module clarity **Component**: Core configuration **Size**: 746 lines → target 4 focused modules ## Problem `src/config.py` is a 746-line monolith handling: - Infrastructure configuration (routers, providers) - Dashboard settings (Flask, UI config) - Timmy-specific configuration (sovereignty, tools) - Integration settings (Discord, Mumble, etc.) This violates single responsibility and makes changes risky. ## Proposed Split ``` src/config/ ├── __init__.py # Main config interface ├── infrastructure.py # Router, provider, hermes config ├── dashboard.py # Flask app, UI settings ├── timmy.py # Sovereignty, tools, core Timmy └── integrations.py # Discord, Mumble, chat bridges ``` ## Files Modified - `src/config.py` (746 lines → ~50 lines coordinator) - `src/config/infrastructure.py` (~200 lines) - `src/config/dashboard.py` (~150 lines) - `src/config/timmy.py` (~200 lines) - `src/config/integrations.py` (~150 lines) ## Acceptance Criteria - [ ] All imports still work (backward compatibility) - [ ] No configuration values lost or changed - [ ] Tests pass without modification - [ ] Each module has single, clear responsibility - [ ] Import paths updated throughout codebase Clean configuration architecture.
Timmy commented 2026-03-24 11:02:10 +00:00
Author
Owner
Copy Link

Assignment to Kimi - Configuration Refactor

Your Task

Refactor the monolithic src/config.py (746 lines) into focused modules while maintaining full backward compatibility.

Specific Steps

  1. Create the new structure:

    src/config/
├── __init__.py          # Re-export everything for compatibility
├── infrastructure.py    # Router, provider, hermes config  
├── dashboard.py         # Flask app, UI settings
├── timmy.py            # Sovereignty, tools, core Timmy
└── integrations.py     # Discord, Mumble, chat bridges

  2. Migration approach:

    • Copy relevant sections from config.py to each new module
    • Update config/__init__.py to re-export all public symbols
    • Keep src/config.py as a compatibility layer initially

Critical Requirements

  • ZERO BREAKING CHANGES: All existing imports must continue to work
  • Configuration values preserved: No settings lost or modified
  • Test compatibility: All tests must pass without modification

Files to Modify

  • Create: src/config/__init__.py
  • Create: src/config/infrastructure.py
  • Create: src/config/dashboard.py
  • Create: src/config/timmy.py
  • Create: src/config/integrations.py
  • Review: src/config.py (understand current structure)

Verification

  1. tox -e unit - all tests pass
  2. python -c "from config import *" - no import errors
  3. git diff --name-only - only new files and config changes

Focus on clean separation while maintaining compatibility.

**Assignment to Kimi - Configuration Refactor** ## Your Task Refactor the monolithic `src/config.py` (746 lines) into focused modules while maintaining full backward compatibility. ## Specific Steps 1. **Create the new structure**: ``` src/config/ ├── __init__.py # Re-export everything for compatibility ├── infrastructure.py # Router, provider, hermes config ├── dashboard.py # Flask app, UI settings ├── timmy.py # Sovereignty, tools, core Timmy └── integrations.py # Discord, Mumble, chat bridges ``` 2. **Migration approach**: - Copy relevant sections from config.py to each new module - Update `config/__init__.py` to re-export all public symbols - Keep `src/config.py` as a compatibility layer initially ## Critical Requirements - **ZERO BREAKING CHANGES**: All existing imports must continue to work - **Configuration values preserved**: No settings lost or modified - **Test compatibility**: All tests must pass without modification ## Files to Modify - Create: `src/config/__init__.py` - Create: `src/config/infrastructure.py` - Create: `src/config/dashboard.py` - Create: `src/config/timmy.py` - Create: `src/config/integrations.py` - Review: `src/config.py` (understand current structure) ## Verification 1. `tox -e unit` - all tests pass 2. `python -c "from config import *"` - no import errors 3. `git diff --name-only` - only new files and config changes **Focus on clean separation while maintaining compatibility.**
kimi was assigned by Timmy 2026-03-24 11:02:15 +00:00
kimi was unassigned by Timmy 2026-03-24 19:33:32 +00:00
Timmy commented 2026-03-24 20:08:57 +00:00
Author
Owner
Copy Link

[triage] Duplicate of #1443 (split config.py). Closing to reduce queue noise.

[triage] Duplicate of #1443 (split config.py). Closing to reduce queue noise.
Timmy closed this issue 2026-03-24 20:08:58 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#1383
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?