ahmza.com/mcpacks
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Move publishing to organization namespace
Publish Packwiz site / publish (push) Canceled after 0s
Details

Browse Source
This commit is contained in:
ahmza
2026-09-04 12:46:31 +00:00
parent 4749e800a3
commit a41e119720
3 changed files with 11 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitea/README.md
+6 -5
View File
@@ -175,17 +175,18 @@ Kubernetes/SWS provides static hosting for the published Packwiz repositories.
The publishing workflow runs [`scripts/build-site.sh`](../scripts/build-site.sh),
which exports committed Git revisions into the documented URL layout, then
builds the multi-architecture image
`tea.ahmza.com/ahmza/mcpacks-site`.
`tea.ahmza.com/ahmza.com/mcpacks-site`.
The workflow finally commits that image's immutable OCI digest to
`apps/mcpacks/deployment.yaml` in the `ahmza/k8s-starter-pack` repository.
`apps/mcpacks/deployment.yaml` in the `ahmza.com/k8s-starter-pack` repository.
Argo CD notices that commit and performs the rollout; the workflow does not
hold Kubernetes credentials or change the cluster directly.
The Gitea Actions repository secret `GITEATOKEN` must be able to:
The Gitea Actions repository secret `GITEATOKEN` must belong to `ci-bot`
and be able to:
- push packages owned by `ahmza`
- read and write `ahmza/k8s-starter-pack`
- push packages owned by the `ahmza.com` organization
- read and write `ahmza.com/k8s-starter-pack`
The `latest` image tag exists only to bootstrap the first Argo CD sync and for
human inspection. Normal rollouts use the exact content digest recorded in the