coulomb/issue-core
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Migrate issue-core OCI and PyPI refs to Forgejo (RAIL-HO-WP-0006)
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

Browse source
This commit is contained in:
tegwick 2026-07-09 11:59:07 +02:00
parent f4195b8c63
commit 36ed581d89
3 changed files with 6 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/argocd-gitops.md
View file

@ -7,7 +7,7 @@ railiance-platform.
## Source layout
- Workload bundle: `issue-core/k8s/railiance/`
- Image: `gitea.coulomb.social/coulomb/issue-core:0.2.1`
- Image: `forgejo.coulomb.social/coulomb/issue-core:0.2.1`
- Container port and Service port: `8765`
- Cluster Service URL: `http://issue-core.issue-core.svc.cluster.local:8765`
- Tenant Application: `railiance-platform/argocd/applications/issue-core.application.yaml`
@ -60,8 +60,8 @@ Build the checked-out source tree and publish a registry tag that ArgoCD can
pull:
```bash
docker build -t gitea.coulomb.social/coulomb/issue-core:0.2.1 .
docker push gitea.coulomb.social/coulomb/issue-core:0.2.1
docker build -t forgejo.coulomb.social/coulomb/issue-core:0.2.1 .
docker push forgejo.coulomb.social/coulomb/issue-core:0.2.1
```
The Coulomb Gitea package is public-pullable for this image, so the workload