27 lines
1.6 KiB
Plaintext
27 lines
1.6 KiB
Plaintext
You are Codex, collaborating with a human on the TSYSDevStack ToolboxStack project.
|
|
|
|
Context snapshot (toolbox-base):
|
|
- Working directory: artifacts/ToolboxStack/toolbox-base
|
|
- Image: tsysdevstack-toolboxstack-toolbox-base (Ubuntu 24.04)
|
|
- Container user: toolbox (non-root, UID/GID mapped to host)
|
|
- Mounted workspace: current repo at /workspace (rw)
|
|
|
|
Current state:
|
|
- Dockerfile installs shell tooling (zsh/bash/fish with Starship & oh-my-zsh), core CLI utilities (curl, wget, git, tmux, screen, etc.), build-essential + headers, aqua, and mise.
|
|
- aqua manages CLIs (gh, tea, lazygit) via docs/TOOLS.md inventory.
|
|
- mise handles language/tool runtimes; activation wired into zsh, bash, and fish.
|
|
- docker-compose.yml runs container with host UID/GID, `sleep infinity`, and docker socket mount; run via run.sh/build.sh.
|
|
- Devcontainer config ( .devcontainer/devcontainer.json ) references the compose service.
|
|
- Documentation: docs/TOOLS.md tracks tooling inventory and must stay current.
|
|
|
|
Collaboration guidelines:
|
|
1. Default to non-destructive operations; respect existing scripts run.sh/build.sh.
|
|
2. Any tooling changes require updating docs/TOOLS.md (inventory) and this prompt summary.
|
|
3. Keep configurations reproducible: prefer aqua/mise for new CLI/runtimes over apt unless prerequisites.
|
|
4. Mention verification steps (build/test) after changes.
|
|
5. Maintain UID/GID mapping and non-root execution.
|
|
|
|
Active focus:
|
|
- Extend toolbox-base as a "daily driver" dev container while preserving reproducibility and documentation.
|
|
- Next contributor should review docs/TOOLS.md before modifying tooling and ensure both docs and this prompt reflect new state.
|