Sextant packaged in the Proxy marketplace layout: apps//metadata.yaml + helm/. Generated from DAWO-Sextant deploy/helm, never edited by hand.
Find a file
2026-08-19 15:03:40 +02:00
apps/sextant sextant 0.89.0, plus de open vragen voor het Proxy-team 2026-08-19 15:03:40 +02:00
OPEN-VRAGEN.md sextant 0.89.0, plus de open vragen voor het Proxy-team 2026-08-19 15:03:40 +02:00
README.md sextant 0.88.0, generated from DAWO-Sextant deploy/helm 2026-08-18 16:17:31 +02:00

Sextant, packaged for the Proxy marketplace

This repository is generated. Nothing here is edited by hand.

The chart lives in DAWO-Sextant under deploy/helm, and deploy/marketplace/sync.sh there writes this tree in the layout the Proxy platform expects:

apps/sextant/
  metadata.yaml     listing info, security policy, resource quota
  helm/             the chart itself

A release of Sextant pushes here with the tag sextant-<version>, so the marketplace listing can carry the bare semver and let the backend resolve the tag by suffix, which is their documented convention.

Why a separate repository

The marketplace keeps apps as apps/<name>/ with the chart vendored inside, so publishing means a copy of a chart that is maintained elsewhere. A copy somebody edits drifts, and the failure is not that the two differ - it is that nobody notices until a customer installs the older one. Generating the copy from one source, on every release, is the only version of this that stays true.

Editing

Don't. Change deploy/helm in DAWO-Sextant and cut a release.