Skip to content

rethink development

The reference for building and shipping on our network: the shared libraries, the coding standards, and how to get a project deployed.

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/....

Point your coding agent here

Want your agent aware of our libraries, standards, and deploy rules before it writes a line? Tell it to read this handbook — so it reaches for an existing rethink-public lib instead of reinventing it, follows our conventions, and builds a deploy-ready container.

Read https://docs.rethinkstudios.io and follow it: prefer our
rethink-public libraries, match our coding standards, and make anything
deployable per the deploy guide.

Point it straight at the repo — no need to clone into your project:

Read the markdown under docs/ in
https://git.rethinkstudios.io/rethink-public/handbook and follow it:
prefer our rethink-public libraries, match our coding standards, and make
anything deployable per the deploy guide. Clone to /tmp if you need it
local.

Sections

  • Libraries

    The live list of the rethink-public library suite, pulled straight from Gitea — each entry links to the repo, where the README and tags live.

  • Standards

    House coding standards — file hygiene, docstrings, type hints, linting, and how we handle errors.

  • Workflow

    Get hands on with how we dev — our Gitea, git habits, and the plan-in-chat / build-in-Claude-Code flow, plus shell setup.

  • Virtual environments

    Project-based Python isolation — local .venv, Makefile, or Docker — and local version management with pyenv.

  • Deploy

    How to get a project running on rethink-net — containers, paths and mounts, permissions, and secrets.