Skip to content

v0.21.0

Choose a tag to compare

View all tags
@mortenoh mortenoh released this 24 Apr 21:08
· 73 commits to main since this release
v0.21.0
This tag was signed with the committer’s verified signature.
mortenoh Morten Hansen
SSH Key Fingerprint: aYrJdVX7f5Swav7umK06M8H6hoV5rjHJADdznk7H83A
Verified
Learn about vigilant mode.
38e2336
This commit was signed with the committer’s verified signature.
mortenoh Morten Hansen
SSH Key Fingerprint: aYrJdVX7f5Swav7umK06M8H6hoV5rjHJADdznk7H83A
Verified
Learn about vigilant mode.

Highlights

Deploying-to-chap-core guide (#40)

New end-to-end guide walking from chapkit init to a model registered with chap-core and visible in the DHIS2 Modeling App:

  • MLServiceInfo fields that operators see in DHIS2
  • Dockerfile layering on chapkit-images (chapkit-py, chapkit-r, chapkit-r-inla)
  • Minimal GHCR publish workflow (3 steps)
  • Compose overlay template with the $$register escape gotcha
  • Troubleshooting for the common "service never appears in GET /v2/services" cases

Uses chapkit_ewars_model as the worked example. Read: Deploying to chap-core.

Self-registration enabled by default in init templates (#40)

chapkit init scaffolds now ship with .with_registration() active at the end of the builder chain — matching the chapkit migrate template. No behaviour change for local python main.py runs (the call silently no-ops when SERVICEKIT_ORCHESTRATOR_URL is unset); scaffolded services drop straight onto a chap-core compose network and self-register without any template edits.

Full changelog: v0.20.0...v0.21.0

Assets 2
Loading