Note
This repository is the main development environment for all my professional and personal projects, including libraries, applications, infrastructure and some private components.
Warning: Expect a developer-centric experience within a complex monorepo structure π
Always evolving code, a wisdom rabbit hole to know the ins and outs of the system as a whole. I could only hope to ever have it all properly documented, as the focus is always on the code itself.
- This readme is intentionally vague in a sense, as there's just too much going on. Instead of talking about everything and nothing at the same time, go exploring the self-documented codebase!
- Feel free to get in touch to learn how it works or python monorepos advice.
Roughly speaking, the important parts are:
π/.github: Workflows, readmes + special organization repositoryπ/website: Mkdocs documentation derived frommkdocs-base.yml
π/docker: Everything docker for all projectsπ/meta: Optional directory to link off-branch projectsπ/projects: Application projects (has entry points)π/packages: Library projects (action.yml: Setup workflow
π/.venv: Global venv from uvπ/broken: Main shared libraryπ/dist: Common build directory
π/crates: Library projectsπ/target: Build directory
- Export
PYTHONPYCACHEPREFIX=/tmp/__pycache__in/etc/environmentto avoid*.pycclutter - Always run
uv sync --all-packagesoruv sync --package (name)for select projects - Use
docker compose run --rm --build (service)fromdocker-compose.yml
