Welcome to the Chap modelling platform!
This is the main repository for the Chap modelling platform.
Read more about the Chap project here
Code documentation
The main documentation for the modelling platform is located at https://chap.dhis2.org/chap-modeling-platform/.
Development / contribution
Information about how to contribute to the Chap Modelling Platform: https://chap.dhis2.org/chap-modeling-platform/contributor/.
Issues/Bugs
If you find any bugs or issues when using this code base, we appreciate it if you file a bug report here: https://github.com/dhis2-chap/chap-core/issues/new
Launch development instance using Docker
cp .env.example .env
docker compose up
Rebuilding after a source change
docker compose up will reuse an existing chap-core-chap image if one is
already built — it does not automatically rebuild when you edit source. If
you see a stale chap_core.__version__ or a fix that clearly didn't land
inside the running container, use one of:
make restart # down && up -d --build (preserves volumes incl. chap-db)
make force-restart # down -v && build --no-cache && up (WIPES VOLUMES)
make chap-version # print the chap_core version running inside the container
make restart is the right hammer 90% of the time. make force-restart
also wipes the Postgres volume, so reach for it only when you need a clean
slate. make chap-version is also printed automatically at the end of
make restart so version drift is visible at a glance.
Running with chapkit model overlays
Chapkit-based models ship as opt-in compose overlays. Layer one onto
compose.yml (not compose.ghcr.yml — those two are alternatives, not
stackable) to run chap-core with the chapkit services already
self-registered.
The recommended overlay is compose.chapkit.yml, an umbrella file that
includes every chapkit-converted model. As more models are converted to
chapkit, they get added here so a single -f flag pulls them all in:
docker compose -f compose.yml -f compose.chapkit.yml up -d
If you only want the EWARS service, use the single-model overlay
compose.ewars.yml instead:
docker compose -f compose.yml -f compose.ewars.yml up -d
Deploy on Kubernetes
CHAP can be deployed on Kubernetes using our helm chart which can be found here.
Metadata
Release files for chap-core 2.3.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 | |
|---|---|---|---|
| chap_core-2.3.1.tar.gz | 345.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| chap_core-2.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 799.5 kB
Release files / chap_core-2.3.1.tar.gz
| Download URL | chap_core-2.3.1.tar.gz |
|---|---|
| Size | 345.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cd7fd7c456fd5d4ca8a97dc418d0a2f1519216aa3bc9d56f41d12b35d582d180
|
|
BLAKE2b-256 checksum How to use checksums |
190554bfe77f4c9ecd61dcb34e9ad0054b2d8d71acb69990bc30dcd629b2897a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 21, 2026.
Transparency logRelease files / chap_core-2.3.1-py3-none-any.whl
| Download URL | chap_core-2.3.1-py3-none-any.whl |
|---|---|
| Size | 454.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f2673113949b81a7978b11529eb2eaf282282038de49615fbdd40a521715c917
|
|
BLAKE2b-256 checksum How to use checksums |
72e53616985b84a90a25cfb2d2105da6b54da2fadfe09d5846bd14b48e073d29
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 21, 2026.
Transparency log
