tegwick
783c8cebbd
Per ADR-002 (railiance-hosts/docs/adr/ADR-002-repo-boundary-hosts-vs-bootstrap.md): - ansible/harden.yml: replaced with tombstone pointing to railiance-hosts - ansible/bootstrap.yml: remove `import_playbook: harden.yml`; add pre-condition comment; OS hardening is no longer this repo's concern - docs/first_host.md: rewritten to reflect 3-step flow: converge railiance-hosts → railiance-bootstrap k3s install → smoke test - workplans/RAIL-BS-WP-0002-k3s-baseline.md: new workplan for k3s + Helm + Kubernetes platform baseline; linked to repo goal 70ab2379 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.