This repo carried a copied declaration identifying it as the S2 cluster runtime layer - byte-similar to railiance-cluster, with which it shares no git history but nearly all of its content. It was one of four repos (bootstrap, cluster, hosts, infra) created by copying working trees as the S1/S2 layering idea emerged, and the INTENT was copied along with everything else. Its own QUICKSTART.md - set up your very first Railiance host - describes what the repo is actually for. INTENT.md and SCOPE.md now declare that: turning a single bare virtual machine into a working Railiance, then handing off to the ordinary layers. Inherited S2-era content in ansible/, helm/, docs/ and wiki/ is not yet sorted; SCOPE records that restructuring is in progress rather than claiming it is done. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .claude/rules | ||
| .forgejo/workflows | ||
| .github/workflows | ||
| ansible | ||
| bin | ||
| cloudinit | ||
| docs | ||
| examples/railiance | ||
| helm | ||
| lib | ||
| registry | ||
| schemas | ||
| tests | ||
| tools | ||
| wiki | ||
| workplans | ||
| .custodian-brief.md | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .repo-classification.yaml | ||
| .sops.yaml | ||
| AGENTS.md | ||
| CLAUDE.md | ||
| DECISIONS.md | ||
| INTENT.md | ||
| LICENSE | ||
| Makefile | ||
| pyproject.toml | ||
| QUICKSTART.md | ||
| README.md | ||
| sbom-tools.yaml | ||
| SCOPE.md | ||
| uv.lock | ||
Railiance Cluster
Opinionated Infrastructure-as-Code framework for reproducible, self-reliant systems.
Railiance is an opinionated Infrastructure-as-Code framework —
think Rails for Ops: convention over configuration, reproducibility first.
This repo (railiance-cluster) is the cluster runtime entry point:
from two bare Linux servers, a Git repo, and credentials, you can rebuild
a fully automated Kubernetes-based environment.
🚀 Quick Start
-
Clone this repo
git clone <your-gitea-url>/railiance-cluster.git cd railiance-cluster -
Configure Gitea access
Edit~/.railiance_gitea.confwith your server URL, username, and token.
(Never commit this file!) -
Bootstrap a host
Run the Ansible playbooks inansible/to set up k3s, Helm, kubectl. -
Deploy baseline services
Usehelm/charts to roll out essential services (GitOps, monitoring, etc.). -
Validate
Check the automated tests intests/to confirm infra health.
📂 Repo Structure
ansible/— Playbooks for provisioninghelm/— Opinionated Helm chartsk8s/— Kubernetes manifeststests/— Automated validationdocs/— Documentation (see docs/README.md)tools/— Helper scripts (e.g.create_railiance_repo.sh)
🤝 Contributing
See docs/CONTRIBUTING.md.
🌍 Vision
Railiance aims for self-reliant infrastructure:
automation you can rebuild from scratch, with calmness and clarity.
From bare metal to resilient clusters — in one repo.