How jauderho/sandbox works
Project type and purpose
• This is a “sandbox” monorepo of dozens of small, standalone tools and utilities (mostly Python-based) packaged as Docker containers for experimentation.
File structure
• Top‐level:
– Configuration and policies (.allstar, .github/, SECURITY.md, CODE_OF_CONDUCT).
– Root‐level Dockerfile (probably builds a generic sandbox or base image).
– scripts/ folder containing utility scripts to update dependencies.
• Each tool directory (e.g. awscli/, datasette/, jless/, open-interpreter/) contains:
– A Dockerfile (often multiple variants: ubuntu, alpine, curl).
– A Python dependency manifest (requirements.txt, Pipfile or pyproject.toml).
– A lock file (uv.lock, Pipfile.lock) where applicable.
Elements
• Clear component labels: Repo, CI/CD, Tool A, Tool B, Scripts, Registry, Developer.
– Repo → GitHub Actions (code push triggers).
– GitHub Actions → Docker Builds (per-tool).
– Docker Builds → Container Registry (publish).
– Developer ↔ Docker Containers (local pulls/runs).
– Another for “CI/CD pipeline.”
– Another for “build artifacts/containers.”