Intech/infra
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
No description
141 commits 2 branches 0 tags 547 KiB
  • JavaScript 49.4%
  • HTML 23.7%
  • Python 17.6%
  • Shell 3.9%
  • Dockerfile 2.9%
  • Other 2.5%
Find a file
Exact
Claude b0bef9b88b fix: point opencode agent at forgejo (entrypoint repo URL + MCP server) 
The entrypoint re-sets the git remote to the decommissioned gitea host on
every container start, crashlooping opencode-web since the registry
migration. GITEA_DEPLOY_TOKEN secret now holds a forgejo token.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-04 12:50:25 -04:00
k3s feat: complete gitea->forgejo registry migration, remove council-pipeline 2026-07-04 12:27:26 -04:00
resources fix: point opencode agent at forgejo (entrypoint repo URL + MCP server) 2026-07-04 12:50:25 -04:00
rss/presentation Replace dead 12ft.io with archive.ph for paywall bypass 2026-05-26 20:14:20 +00:00
AGENTS.md feat: complete gitea->forgejo registry migration, remove council-pipeline 2026-07-04 12:27:26 -04:00
monitoring.md refactor: simplify agent config, update docs for current cluster state 2026-03-09 02:36:51 +00:00
opencode.json Set context/output limits for GLM 5 to fix hang in OpenCode 2026-04-01 01:30:30 +00:00
README.md chore: sync manifests with live cluster state (2026-07-04 healthcheck) 2026-07-04 12:04:57 -04:00

README.md

Infrastructure Monorepo

k3s cluster infrastructure managed via Forgejo at forgejo.ignohr.com/Intech/infra.

Migrated from Docker Swarm to k3s in March 2026. Active deployments are managed via kubectl with manifests in k3s/.

Repository Structure

k3s/
  <service>.yaml              # Single-workspace manifests (top-level)
  <namespace>/                # Multi-resource directories
resources/<name>/             # Dockerfiles, helper scripts, application code
opencode.json                 # Runtime model config for OpenCode
monitoring.md                 # Monitoring guide

Manifest convention: Single-workload services live as k3s/<service>.yaml (e.g., forgejo.yaml, vaultwarden.yaml). Services with multiple related resources get their own k3s/<namespace>/ directory.

Container Registry

Custom images: forgejo.ignohr.com/intech/<name>:<tag> (Forgejo's container registry). The old gitea.ignohr.com registry is decommissioned (Gitea scaled to 0) — do not reference it in manifests.

Live State

The live state is always in the k3s cluster. k3s/ manifests are exported snapshots for version control.

kubectl apply -R -f k3s/        # Apply all
kubectl diff -R -f k3s/          # Check drift