disqualifier
613d8f28ea
New docs/environments.md, nav 'Virtual environments' (before Deploy): - the rule: never touch system Python (danger callout) - project-based isolation as Local .venv / Makefile-driven / Docker tabs, each with a runnable snippet; Docker ties back to the deploy standard - local dev with pyenv: why, official install link, shell init with annotated lines, everyday use, per-project .python-version - shell quality-of-life extras (flake8 alias, .local/bin + npm-global PATH), cross-ref'd to Standards and Workflow workflow.md pyenv bullet now points at the new page; index.md gains a card. Verified in-browser: tabs switch (Local/Makefile/Docker), annotations and admonitions render; mkdocs build --strict clean (cross-ref anchors resolve). Signed-off-by: disqualifier <dev@disqualifier.me>
1.4 KiB
rethink development
The public reference for building and shipping with Rethink Studios: our shared libraries, our coding standards, and how to deploy a project on our network.
This is a public site — it documents generic patterns and conventions. Real
infrastructure specifics (hostnames, internal IPs, exact topology, secrets) stay
out of it; examples use placeholders like <dev>, <project>, and /srv/....
Sections
-
:material-package-variant: Libraries
The live list of the
rethink-publiclibrary suite, pulled straight from Gitea — each entry links to the repo, where the README and tags live. -
:material-ruler-square: Standards
House coding standards — file hygiene, docstrings, type hints, linting, and how we handle errors.
-
:material-sitemap: Workflow
How we actually work day to day — our Gitea, git habits, and the plan-in-chat / build-in-Claude-Code flow, plus shell setup.
-
:material-language-python: Virtual environments
Project-based Python isolation — local
.venv, Makefile, or Docker — and local version management with pyenv. -
:material-rocket-launch: Deploy
How to get a project running on rethink-net — containers, paths and mounts, permissions, and secrets.