tegwick
b3b0c3e3ff
- Add RAIL-BS-WP-0008 (activity-core WP-0016 deploy) and RAIL-BS-WP-0009 (admin-sync smoke) from inbox asks 87952ff1 / aa8b7986 - Archive finished workplans to workplans/archived/ per ADR-001 convention; normalize frontmatter statuses (completed/done -> finished) - Fill stack-and-commands.md, complete repo-boundary.md, refresh SCOPE Current State, add docs/operator-runbook.md for production-touching targets Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.