refactor: move stack assets and wire in mailhog

This commit is contained in:
2025-10-29 05:56:27 -05:00
parent 8f37c46310
commit 7061fbb2a9
41 changed files with 217 additions and 251 deletions

View File

@@ -0,0 +1,63 @@
# New Chat Summary: TSYSDevStack SupportStack End-to-End Build
## Overview
This chat will focus on executing the end-to-end build of the TSYSDevStack SupportStack using the comprehensive prompt file. The implementation will follow strict Test Driven Development (TDD) principles with all requirements specified in the prompt.
## Key Components to Build
1. **docker-socket-proxy** - Enable Docker socket access for containers that need it (not homepage)
2. **homepage** - Configure to access Docker socket directly for automatic label discovery
3. **wakaapi** - Integrate with homepage using proper labels
## Key Requirements from Prompt
- Use atomic commits with conventional commit messages
- Follow strict TDD: Write test → Execute test → Test fails → Write minimal code to pass test
- 75%+ code coverage requirement
- 100% test pass requirement
- Component-by-component development approach
- Complete one component before moving to the next
- All Docker artifacts must be prefixed with `tsysdevstack-supportstack-demo-`
- Run exclusively on localhost (localhost binding only)
- Ephemeral volumes only (no persistent storage)
- Resource limits set for single-user demo capacity
- No external network access (localhost bound only)
- Homepage container needs direct Docker socket access for labels to auto-populate
- Docker socket proxy provides controlled access for other containers that need Docker access
- All containers need proper UID/GID mapping for security
- Docker group GID must be mapped properly for containers using Docker socket
- Non-Docker socket using containers should use invoking UID/GID
- Use SQLite for every service that will support it to avoid heavier databases where possible
- Only use heavier databases when SQLite is not supported or inadequate for the service
## Implementation Process
1. Start with docker-socket-proxy (dependency for homepage)
2. Implement homepage (requires docker-socket-proxy)
3. Implement wakaapi (integrates with homepage)
4. Validate all components work together with proper service discovery
5. Run comprehensive test suite with >75% coverage
6. Ensure all tests pass with 100% success rate
## Files to Reference
- **Prompt File**: `/home/localuser/TSYSDevStack/collab/SupportStack/BuildTheStack`
- **Status Tracking**: `/home/localuser/TSYSDevStack/collab/SupportStack/STATUS.md`
- **Human Help**: `/home/localuser/TSYSDevStack/collab/SupportStack/HUMANHELP.md`
- **Production Roadmap**: `/home/localuser/TSYSDevStack/collab/SupportStack/ProdRoadmap.md`
## Directory Structure
All artifacts will be created in:
- `/home/localuser/TSYSDevStack/artifacts/SupportStack/`
## Success Criteria
- ✅ All 3 MVP components implemented and tested
- ✅ Docker socket proxy providing access for homepage discovery
- ✅ Homepage successfully discovering and displaying services through Docker labels
- ✅ WakaAPI properly integrated with homepage via Docker labels
- ✅ All tests passing with 100% success rate
- ✅ Code coverage >75%
- ✅ All containers running with proper resource limits
- ✅ All containers using correct naming convention (`tsysdevstack-supportstack-demo-*`)
- ✅ All containers with proper UID/GID mapping for security
- ✅ All services accessible on localhost only
- ✅ SQLite used for database-backed services where possible
- ✅ Zero technical debt accrued during implementation
Let's begin the end-to-end build process by reading and implementing the requirements from the prompt file!