Repo Aleph
A starting point for Python projects, developed in a VS Code Dev Container. The container uses Python 3.14, uv for environment and dependency management, Poe the Poet for project tasks, and pre-commit for checks and formatting.
Getting Started
Prerequisites:
- Docker
- Visual Studio Code with the Dev Containers extension
Open the repository in VS Code and run Dev Containers: Reopen in Container from the Command Palette. On first creation, the container installs the project dependencies with uv sync, configures shell completions, installs OpenCode and APM, and installs the Git pre-commit hooks.
The project requires Python 3.14 or newer (requires-python in pyproject.toml); the development container currently uses Python 3.14 on Debian Trixie.
Poe Tasks
Poe tasks are declared in poe.toml. In the container, a poe shell command is provided that runs Poe through uv; you can also invoke it explicitly with uv run poe.
| Command | What it does |
|---|---|
poe fmt |
Formats Python code with uv format. |
poe pre-commit |
Runs all configured pre-commit hooks against all files. |
poe --help |
Lists available tasks. |
The same tasks can be run outside the container as uv run poe fmt and uv run poe pre-commit. The current task list is intentionally small; run other tools through uv run, for example uv run pytest or uv run ruff check ..
Dependencies are managed with uv. Add runtime dependencies with uv add <package> and development dependencies with uv add --dev <package>. These commands update pyproject.toml and uv.lock.
What's in the Dev Container
- Python 3.14 on Debian Trixie, plus build tools and the configured certificate trust for network tools.
uv, Node.js 24,pnpm, TypeScript,ts-node, ripgrep, and Docker CLI access through the Docker-outside-of-Docker feature.- Zsh as the default shell, with completions for
uv, Docker, and Poe. - VS Code extensions for Python, Ruff, mypy, Prettier, and Mermaid. Python files use Ruff for format-on-save; JavaScript and TypeScript use Prettier.
- Pre-commit hooks for common file checks, Ruff linting/formatting,
uv.lockconsistency, and Prettier.
The post-create scripts also configure the ys Zsh theme, append shell history to a shared file, install OpenCode and APM, and install the repository's pre-commit hooks. To update the container's tools or features, edit .devcontainer/devcontainer.json, .devcontainer/Dockerfile, or the scripts under .devcontainer/scripts, then rebuild the container.
Persistent Container Data
Docker named volumes keep selected data across container rebuilds:
devcontainer-zshhistorystores Zsh history at/commandhistory/.zsh_history.devcontainer-opencodestores OpenCode's database at/opencode-storage/opencode.db.
These are Docker-managed volumes, not folders in the repository. Removing a volume removes its data; rebuilding the container alone does not.
OpenCode with Host Ollama
OpenCode is installed globally in the container. The sample configuration is in .opencode/opencode.jsonc; it defines an OpenAI-compatible provider named host-ollama with base URL http://host.docker.internal:11434/v1.
This assumes Ollama is running on the host machine and its API is reachable from the container on port 11434. The Dev Container adds host.docker.internal as a route to the host. Start Ollama and make sure its API is available to the container; do not expose it to untrusted networks. The model names in the sample (gemma4:12b-mlx, gemma4:31b-mlx, and qwen3.8:27b-mlx) are examples: replace them with model identifiers available from your Ollama server.
The file is a project sample; if your OpenCode installation does not load it automatically, merge its provider definition into the OpenCode configuration location used by your version. The database path is set separately by the container's OPENCODE_DB environment variable and backed by the persistent volume above.
APM
APM (Agent Package Manager) is installed during container creation. It manages agent packages from a project manifest and installs supported artifacts such as commands, prompts, skills, and MCP servers for the selected agent tools.
The root apm.yml declares copilot and opencode as targets and currently has no APM or MCP dependencies. The copilot target covers GitHub Copilot in both the CLI and IDE, including VS Code. Add dependencies to the manifest and run apm install from the repository root to install them for the selected targets; use apm --help to see the available commands.
Common Commands
# Install/synchronize project dependencies
uv sync
# Run the available project tasks
poe fmt
poe pre-commit
# Run tests and tools that are not currently Poe tasks
uv run pytest
uv run mypy src
uv run pyright
Metadata
Release files for repo-aleph 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| repo_aleph-0.0.1.tar.gz | 8.6 kB | With provenance | Details for repo_aleph-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| repo_aleph-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for repo_aleph-0.0.1-py3-none-any.whl |
Total release size: 17.7 kB
Release files / repo_aleph-0.0.1.tar.gz
| Download URL | repo_aleph-0.0.1.tar.gz |
|---|---|
| Size | 8.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
74bbdc000336ad4a6e4b861d532af24321211d0f130d61f4360a592291847aa7
|
|
BLAKE2b-256 checksum How to use checksums |
45f404795f9895dbfbead12c7d1c6946b1f0716bf2868aee2a4a0ed8e010fad5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 14, 2026.
Transparency logRelease files / repo_aleph-0.0.1-py3-none-any.whl
| Download URL | repo_aleph-0.0.1-py3-none-any.whl |
|---|---|
| Size | 9.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ed3bd3b7a6c2e5209fbce41ea274bd28787def2005aac079bf976f40dccea129
|
|
BLAKE2b-256 checksum How to use checksums |
dcba991cd5dfcaea6c5cce75b31db9e8e91fc866f1fdb6aa69ec41cc775755c6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 14, 2026.
Transparency logSecurity for repo-aleph 0.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for repo_aleph-0.0.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 14, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.