Skip to content

armgit / ODS

Public Imported from GitHub
0

ODS V3 Pre-Release: Public testing and refinement ahead of the official V3 launch. Turn your PC, Mac, or Linux box into a private AI server.

2.1 KB
Raw Blame

Runtime dependency locks

The nine Python API/relay images install requirements.lock with pip's --require-hashes. requirements.txt is the human-maintained input, not the production installer input. Locks include all transitive distributions and upstream SHA-256 hashes for the supported platform wheels.

After changing an input, regenerate its adjacent lock from the repository root:

python -m pip install uv==0.12.19
uv pip compile ods/extensions/services/dashboard-api/requirements.txt \
  --universal --python-version 3.11 --generate-hashes --no-header \
  --no-annotate --index-url https://pypi.org/simple \
  -o ods/extensions/services/dashboard-api/requirements.lock

The dashboard API requires Python 3.11 or newer, matching its production container and Pillow 13. Use --python-version 3.10 when replacing dashboard-api with another service; their existing lock targets are unchanged. This does not change the installer host-Python requirement. Existing versions are retained where they still satisfy the inputs; use --upgrade-package NAME for a reviewed transitive update. Commit the input and lock together. Do not edit hashes or ignore advisories to make a build pass.

security-runtime.yml verifies regeneration without drift, installs each lock using its image's Python minor version, checks dependency consistency, and runs pip-audit --require-hashes on the production lock. The weekly run catches new advisories even when no dependency file has changed. Dashboard production dependencies are audited separately from development tools.

The same workflow also installs and audits Web Courier's shipped hashed lock and the exact dependency lists used by the optional Datasette and Radicale images. These paths are outside the nine API/relay lock sets. Their audits include every pinned distribution; they do not suppress transitive advisories.

Hashes verify downloaded package bytes; they do not establish that an upstream package is benign. Security review, vulnerability audits and integration tests remain necessary. Docker OS packages and release provenance are separate checks.