Comparing b12527b11e..d74e7964a6 - docs - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
technical-writer	d74e7964a6	fix(tutorials): correct env vars, healthcheck paths, Python code, and grace period Secret scan / secret-scan (pull_request) Successful in 1m16s Details CI / build (pull_request) Successful in 4m33s Details Corrections from PR #40 (docs/self-hosted-workspace-docker SHA `b12527b`): - PLATFORM_URL (not MOLECULE_API_URL) — verified against workspace/main.py:85 - Remove MOLECULE_API_KEY and AGENT_CARD_URL from env vars table (not real env vars) - Healthcheck path: /.well-known/agent-card.json (not /agent/card) — verified via boot_routes.py - Python: use HeartbeatLoop (not fabricated RemoteAgentClient) - terminationGracePeriodSeconds: 120 — probe failure window is 120-150s (not 90s) - Docker Compose: remove MOLECULE_API_KEY, fix healthcheck path - Troubleshooting: MOLECULE_API_URL → PLATFORM_URL Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-05-15 08:01:40 +00:00
documentation-specialist	4ae1a322fc	ci: add explicit timeout-minutes to CI build job Secret scan / secret-scan (pull_request) Successful in 1m32s Details CI / build (pull_request) Successful in 4m23s Details Gitea Actions default runner timeout is ~15min. Add explicit timeout-minutes: 30 to prevent false failures on slow/unprovisioned runner instances. The content builds successfully in <5min locally. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-05-15 06:12:08 +00:00
documentation-specialist	8fdfc2dd3a	ci: retrigger build to clear stale failure status Secret scan / secret-scan (pull_request) Successful in 1m18s Details CI / build (pull_request) Successful in 5m20s Details Force-push to re-trigger CI on a clean runner. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-05-15 05:26:36 +00:00
documentation-specialist	644226f2b2	fix(docs): set terminationGracePeriodSeconds to 120 in Kubernetes YAML example Secret scan / secret-scan (pull_request) Successful in 1s Details CI / build (pull_request) Successful in 4m4s Details The example showed terminationGracePeriodSeconds: 30, but the accompanying note says the value "should exceed the healthcheck failure threshold (3 × 30s = 90s)". With 30s < 90s, Kubernetes would send SIGTERM and wait only 30s before SIGKILL — potentially killing the pod before the graceful shutdown (3s via stop_event) completes. Changed to 120s, which exceeds the 90s threshold and aligns the YAML example with the documented requirement. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-05-15 04:57:26 +00:00

1 changed files with 1 additions and 0 deletions

									
										.gitea/workflows/ci.yml
									
		+1
		
												View File
												
				@@ -7,6 +7,7 @@ on:

				jobs:

				  build:

				    runs-on: ubuntu-latest

				    timeout-minutes: 30

				    steps:

				      - uses: actions/checkout@v4

				      - uses: actions/setup-node@v4

Compare commits

4 Commits

pr-40-review .. pr-46

Compare commits

4 Commits pr-40-review .. pr-46

4 Commits

pr-40-review .. pr-46