Align chart tag with application 2.4.69-8.5.11
Publish PHP Apache image / Build, test and push (push) Successful in 40s

This commit is contained in:
2026-10-19 17:31:53 +02:00
parent 14e1250b59
commit 215313e9cb
2 changed files with 16 additions and 5 deletions
+11 -5
View File
@@ -44,14 +44,20 @@ The chart can create a new RWX PVC when `existingClaim` is empty. Such PVCs
carry Helm's `keep` resource policy by default as an additional safeguard for
website content.
Each successful `main` or scheduled image build also publishes a new chart to
the `feedc0de` Gitea Helm registry. Its `appVersion` is the unique image tag
built by that same workflow run. Site values do not override the image, so
updating the Helm repository and upgrading a release selects the image from the
new chart:
Each successful `main` push also publishes a new chart to the `feedc0de`
Gitea Helm registry. Scheduled builds refresh the image tags without
publishing a chart. The chart's `appVersion` is the unique image tag built by
the same push. Site values do not override the image, so updating the Helm
repository and upgrading a release selects the image from the new chart:
```sh
helm repo add brunner.ninja https://brunner.ninja/charts
helm repo update brunner.ninja
helm upgrade --install example-site brunner.ninja/php-homepage -f values.yaml
```
The chart repository tag follows the bundled Apache and PHP versions. The
current image contains Apache 2.4.69 and PHP 8.5.11, so `v2.4.69-8.5.11`
publishes chart `2.4.69-8.5.11`; later chart commits append the Git describe
count and hash. CI checks the built image's versions against the base Git tag
before publishing a chart.