forust/homelab
0
0 Fork 0
Code Issues 1 Pull Requests 4 Actions Packages Wiki Activity

Add CI and deploy summaries
ci / Compose (push) Skipped
ci / Workflows (push) Skipped
ci / Shell (push) Skipped
ci / Formatting (push) Skipped
ci / Python and tests (push) Skipped
ci / YAML (push) Skipped
ci / Kubernetes (push) Skipped
ci / Dockerfiles (push) Skipped
ci / Compose (pull_request) Successful in 14s
Details
ci / Workflows (pull_request) Successful in 7s
Details
ci / Shell (pull_request) Successful in 23s
Details
ci / Formatting (pull_request) Successful in 26s
Details
ci / Python and tests (pull_request) Successful in 8s
Details
ci / YAML (pull_request) Successful in 14s
Details
ci / Dockerfiles (pull_request) Successful in 7s
Details
ci / Kubernetes (pull_request) Successful in 10s
Details
ci / build (pull_request) Skipped
Details

Browse Source
This commit is contained in:
forust committed 2026-10-06 23:28:56 +02:00
1 parent b677d553b4
commit d74822cd27
4 files changed
+89 -3
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

.gitea/runner/README.md
+3 -1
View File
@@ -3,7 +3,9 @@
The native Gitea runner runs on **vps**; production runs on **workstation**.
Compose, workflow, shell, Python, formatting, YAML, Dockerfile and Kubernetes
checks appear as separate jobs. Jobs run on `homelab:host`, one at a time; the
build waits for every check to pass. No job images or Kubernetes credentials
build waits for every check to pass. CI and deploy runs also show a summary with
the release SHA, image build or reuse results, deploy mode, selected services,
and image digests. No job images or Kubernetes credentials
are needed on the VPS. Builds use one pinned BuildKit helper container. CI and deploy are separate workflows.
## Runner installation