Bernd Worsch
66f8ca4009
T02: note to verify etcd is in use before implementing; flags root requirement
T03: add KUBECONFIG to helm commands; note root access approach
T06: document solution to sudo problem — run cron under root's crontab,
not a sudoers whitelist. Add restore drill commands. Fix cron to use
absolute path (~ unreliable in root crontab).
T01: note to remove old railiance-backup script (wrong scope)
Makefile: fix stale backup description, add restore target, fix .PHONY
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.