KNEL/TSYSDevStack
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
main
TSYSDevStack/SupportStack/QWEN.md
ReachableCEO 9fbacb2cdf docs(qwen): refine git responsibilities across QWEN.md files 
- Update top-level QWEN.md to include details about git template work across all stacks
- Remove all git configuration details from CloudronStack/QWEN.md, leaving only the Topside git operations notice
- Remove all git configuration details from LifecycleStack/QWEN.md, leaving only the Topside git operations notice
- Remove all git configuration details from SupportStack/QWEN.md, leaving only the Topside git operations notice
- Remove all git configuration details from ToolboxStack/QWEN.md, leaving only the Topside git operations notice
- Ensure all subdirectory QWEN.md files contain only the notice about Topside being responsible for git operations
- Consolidate git configuration information in the top-level QWEN.md file

This clarifies git responsibilities while maintaining necessary information about
the git template work in the central location.
2025-10-29 08:19:59 -05:00

3.9 KiB
Raw Permalink Blame History

Qwen Code Context File

Project Overview

The TSYSDevStack SupportStack is a curated demo environment for developer support tools. It bundles Dockerized services, environment settings, automation scripts, and a growing library of collaboration notes. The stack includes tools like Atuin, MailHog, AtomicTracker (habit tracker), local Grafana/InfluxDB for private metrics (Apple health export), WakaAPI and other useful developer productivity and support tools.

Multi-Chat Environment Context

This project operates within a multi-chat system with five QWEN chats working on related but separate directory trees:

  • SupportStack (this chat) - Focused on developer support tools
  • Other sibling directories operate independently but may share common infrastructure patterns
  • All work is confined to the current directory tree only
  • Each chat maintains its own QWEN.md context file

Project Structure

TSYSDevStack/SupportStack/
├── README.md              # Main project documentation
├── collab/                # Collaboration notes, roadmaps, prompts
├── output/                # Main project artifacts
│   ├── code/              # Control script
│   ├── config/            # Service configurations
│   ├── docker-compose/    # Docker Compose files for services
│   ├── docs/              # Documentation
│   ├── tests/             # Test scripts
│   └── TSYSDevStack-SupportStack-Demo-Settings # Environment settings

Key Components

  1. Control Script: Orchestrates start/stop/update/test flows for the demo stack (output/code/TSYSDevStack-SupportStack-Demo-Control.sh)
  2. Environment Settings: Centralized .env style configuration (output/TSYSDevStack-SupportStack-Demo-Settings)
  3. Docker Compose Bundles: Service definitions for developer tools like Atuin, MailHog, AtomicTracker, Grafana/InfluxDB, WakaAPI, and more (output/docker-compose/)
  4. Service Config: Configuration for developer tools mounted into containers (output/config/)
  5. Tests: Shell-based smoke, unit, and discovery tests for stack services (output/tests/)

Current Status

  • Project: TSYSDevStack SupportStack Demo
  • Status: ✅ MVP COMPLETE
  • Last Updated: October 28, 2025

MVP Components

  • docker-socket-proxy: Docker socket access for secure container communication
  • homepage: Homepage dashboard accessible at http://127.0.0.1:4000
  • wakaapi: WakaAPI service accessible at http://127.0.0.1:4001
  • mailhog: Mailhog service for email testing
  • atuin: Shell history with sync and search capabilities
  • atomictracker: Habit tracking application
  • grafana/influxdb: Private metrics collection and visualization

Git Operations Notice

  • IMPORTANT: Git operations (commits and pushes) are handled exclusively by the Topside agent
  • SupportBot should NOT perform git commits or pushes
  • All changes should be coordinated through the Topside agent for repository consistency

Key Technologies

  • Docker
  • Docker Compose
  • Shell scripting
  • Homepage dashboard
  • WakaAPI
  • MailHog
  • Atuin (shell history)
  • AtomicTracker (habit tracking)
  • Grafana/InfluxDB (metrics)
  • Apple health export tools

Important Files

  • Control script: output/code/TSYSDevStack-SupportStack-Demo-Control.sh
  • Environment settings: output/TSYSDevStack-SupportStack-Demo-Settings
  • Docker Compose files: output/docker-compose/
  • Test scripts: output/tests/

Development Notes

  • The stack expects Docker access and creates the shared network tsysdevstack-supportstack-demo-network if it does not exist.
  • Keep demo automation in output/ and exploratory material in collab/.
  • When adding a new service, update both the compose files and the test suite to maintain coverage.
  • Focus on developer productivity and support tools such as Atuin, MailHog, AtomicTracker, Grafana/InfluxDB, WakaAPI, and Apple health export tools.