5 Commits

Include renames

Author	SHA1	Message	Date
ClaudeandClaude Opus 5.5	0f1ed99dfc	Log real client IPs and enable Gitea Actions with a runner ... - Trust X-Forwarded-For from the pod network (10.244.0.0/16) via security.REVERSE_PROXY_TRUSTED_PROXIES / REVERSE_PROXY_LIMIT so Gitea logs the external client address instead of the ingress-nginx pod IP. - Set actions.ENABLED explicitly and deploy an instance-wide runner via the gitea/actions chart (release "gitea-actions", pinned to 0.1.2). The registration token is generated in-cluster and stored in a Secret on first run, so no token lives in git or the vault. - Fix the old actions.yaml, which reused the "gitea" release name and would have clobbered the main Gitea release. - Add a demo workflow (.gitea/workflows/demo.yaml). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-06 12:56:58 -05:00
eric	9f46e92cd7	Catppuccin	2026-10-26 18:55:54 -04:00
eric	a87baf2325	Update	2026-10-23 11:23:04 -04:00
eric	8de7e69a12	Combating spam	2026-04-12 19:09:32 -04:00
eric	b9f615dcb3	Initial commit	2026-02-27 17:30:50 -05:00