- Update ToolboxStack/output/toolbox-base/Dockerfile with latest container settings - Refine container build process and dependencies - Ensure optimal configuration for developer environments This improves the base developer environment container configuration.
🧰 ToolboxStack
ToolboxStack provides reproducible developer workspaces for TSYSDevStack contributors. The current toolbox-base image captures the daily-driver container environment used across the project.
Contents
| Area | Description | Path | 
|---|---|---|
| Dev Container Image | Ubuntu 24.04 base with shell tooling, mise, aqua-managed CLIs, and Docker socket access. | output/toolbox-base/Dockerfile | 
| Build Helpers | Wrapper scripts for building ( build.sh) and running (run.sh) the Compose service. | output/toolbox-base/ | 
| Devcontainer Config | VS Code Remote Container definition referencing the Compose service. | output/toolbox-base/.devcontainer/devcontainer.json | 
| Prompt & Docs | Onboarding prompt plus a feature-rich README for future collaborators. | output/toolbox-base/PROMPT,output/toolbox-base/README.md | 
| Collaboration Notes | Shared design prompts and coordination notes for toolbox evolution. | collab/ | 
Quick Start
cd output/toolbox-base
./build.sh        # build the image with UID/GID matching your host
./run.sh up       # launch the toolbox-base service in the background
docker exec -it tsysdevstack-toolboxstack-toolbox-base zsh
Use ./run.sh down to stop the container when you are finished.
Contribution Tips
- Document every tooling change in both the PROMPTandREADME.md.
- Prefer installing CLIs via aquaand language runtimes viamiseto keep the environment reproducible.
- Keep cache directories (.build-cache/, mise mounts) out of Git—they are already covered by the repo's.gitignore.
🧭 Working Agreement
- Stacks stay in sync. When you add or modify automation, update both the relevant stack README and any linked prompts/docs.
- Collab vs Output. Use collab/for planning and prompts, keep runnable artifacts underoutput/.
- Document forward. New workflows should land alongside tests and a short entry in the appropriate README table.
- AI Agent Coordination. Use Qwen agents for documentation updates, code changes, and maintaining consistency across stacks.
🤖 AI Agent
This stack is maintained by ToolboxBot, an AI agent focused on ToolboxStack workspace management.
📄 License
See LICENSE for full terms. Contributions are welcome—open a discussion in the relevant stack's collab/ area to kick things off.