coulomb/railiance-apps
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
12 Commits 1 Branch 0 Tags
2537ca17b83d616ddece1728baf59f960042e918
Commit Graph

12 Commits

This Branch
This Branch
All Branches
Author SHA1 Message Date
tegwick
2537ca17b8 Refresh agent instruction files 2026-05-18 16:55:48 +02:00
tegwick
e24568cb40 Gitea container repo activation 2026-05-15 23:02:21 +02:00
tegwick
d892cbfb13 chore(consistency): sync task status from DB [auto] 
Updated by fix-consistency on 2026-05-15:
  - update .custodian-brief.md for railiance-apps
 2026-05-15 16:35:19 +02:00
tegwick
2967d1db74 chore(consistency): sync task status from DB [auto] 
Updated by fix-consistency on 2026-05-15:
  - update .custodian-brief.md for railiance-apps
 2026-05-15 15:39:33 +02:00
tegwick
2bb0800072 Scope update from repo-scoping refactor 2026-05-01 12:28:45 +02:00
Bernd Worsch
065d1b02f1 feat(gitea): update Helm values with external DB/cache config and add SOPS policy 
Restores the newer local gitea-values.sops.yaml (2026-03-27) over the
upstream scaffold (2026-03-10). Adds database, cache, session, and queue
sections pointing to external PostgreSQL/Valkey (S3 platform services),
and disables bundled postgresql/redis/valkey sub-charts.

Also adds .sops.yaml encryption policy for railiance-apps.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
 2026-03-31 11:52:54 +00:00
tegwick
49f594ac4d chore(consistency): sync task status from DB [auto] 
Updated by fix-consistency on 2026-03-27:
  - update .custodian-brief.md for railiance-apps
 2026-03-27 13:23:56 +01:00
tegwick
89b777bf6c feat(gitea): take ownership of Gitea Helm values (T06) 
Receive gitea-values.sops.yaml from railiance-cluster — S5 now
owns the Gitea deployment lifecycle per ADR-003 boundary rules.

Add gitea-deploy and gitea-status Makefile targets. Update
SCOPE.md to reflect boundary violation resolved.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
 2026-03-27 13:23:53 +01:00
tegwick
aa83fb5563 feat(gitea): add Helm values with right-sized PGPool CPU request 
PGPool default 250m CPU request was causing scheduling failures on the
single-node COULOMBCORE cluster (2 vCPU, 98% allocated). Reduced to
100m request / 200m limit — safe for a lightweight connection pooler.
See INC-001: the-custodian/ops/incidents/2026-03-25-gitea-pgpool-crashloop.md

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
 2026-03-25 11:30:54 +01:00
tegwick
e8de05b9ab Updated scope 2026-03-20 23:42:20 +01:00
tegwick
2bc59e98c9 docs: add SCOPE.md for rapid orientation 
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
 2026-03-17 23:11:38 +01:00
tegwick
668dfd9b54 chore(init): scaffold railiance-apps (S5 Workloads & Experience Endpoints) 
Initial repo structure per ADR-003: CLAUDE.md, Makefile, workplans/.
No implementation yet — repo claims its OAS stack layer.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
 2026-03-10 00:36:06 +01:00