tegwick
5b0cfbf10a
WP-0004 rewritten: scope narrowed to S2-owned assets (etcd snapshots, Helm values, kubeconfig). No external dependencies. age encryption reuses SOPS key pair. Output to /opt/backup/railiance/cluster/. DECISIONS.md D4: integrated backup per capability, not centralized. EP-RAIL-005 registered in state hub: custodian orchestration deferred until all layers implement the standard interface. The old monolithic backup (custodian DB + operator config) was not S2's concern and has been removed from this workplan scope. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Railiance Bootstrap
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-bootstrap) is the 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-bootstrap.git cd railiance-bootstrap -
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.