Skip to content

Getting Started

Shared HTTP, authentication, browser and application infrastructure packages.

Overview

common-infra is a uv workspace monorepo: every package lives under libs/ as an independently versioned, independently released member. The workspace root owns the shared tooling (lint, types, tests, docs, CI); each member owns its own pyproject.toml, source, and tests.

Prerequisites

  • uv — manages Python, the venv, and all dependencies: curl -LsSf https://astral.sh/uv/install.sh | sh

If this repo consumes private packages, configure your registry read token first — see CONTRIBUTING.md in the repo root for the one-time setup.

Set up a clone

Terminal window
git clone https://github.com/null-capital/common-infra.git
cd common-infra
doppler run --project global --config prd -- ./run sync

./run sync creates the venv, installs all dependencies (uv sync --all-extras), and installs the git hooks. For private packages, the standard doppler run command routes GEMFURY_READ_TOKEN to uv without persisting it.

Install a package

Released versions publish to Gemfury; consumers install with the private index configured:

Terminal window
uv add common-http

For development with every member’s optional dependencies (Playwright, crypto, PostgreSQL), run uv sync --locked --all-packages --all-extras --group dev with the same registry access as the setup command above.

Verify

Terminal window
./run check

./run check runs exactly what CI runs (lint + format + types + test), so green locally means green in CI.

Add a package

Terminal window
./run package add <name> # scaffolds libs/<name> wired into the workspace
./run package remove <name> # exact inverse

New members are discovered by workspace checks and the docs reference. Release automation is explicitly configured in release-please-config.json (http, auth, browser, reports). Reserved core and execution directories remain excluded while their existing releases from the common repository are consumed.

Next steps