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 Documentation
Welcome to Railiance — an opinionated framework for Infrastructure-as-Code.
Think of it as Rails for Ops: convention over configuration, productivity first, reproducible everywhere.
🚀 What is Railiance?
Railiance is the self-reliant infrastructure bootstrap for Coulomb and beyond.
From two bare Linux servers, a Git repo, and valid credentials, you can rebuild a full Kubernetes-based environment with:
- Automated provisioning (Ansible, Helm, k3s)
- Git-driven state (ArgoCD / Flux)
- AI-ready automation with OODA loop (Observe, Orient, Decide, Act)
- End-to-end reproducibility — no hidden steps, no snowflake servers
🌱 Core Principles
-
Convention over configuration
Opinionated defaults remove friction. -
Don’t repeat yourself (DRY)
Single source of truth in Git, reused everywhere. -
Automated OODA
- Observe: collect telemetry.
- Orient: AI interprets state.
- Decide: human reviews & authorizes.
- Act: automation applies changes.
-
Self-Reliance
Everything can be rebuilt from scratch, with no external dependencies beyond Git + credentials. -
Calm Ops
Systems should be simple, resilient, and predictable.
📂 Repo Layout
ansible/— bootstrap playbooks (OS setup, k3s install, etc.)helm/— Helm charts for servicesk8s/— raw manifests & overlaystests/— automated validation of infra stepsdocs/— documentation & contributor guidestools/— helper scripts (e.g. repo bootstrap)
🛠 Getting Started
-
Clone the repo
git clone <your-gitea-url>/railiance-cluster.git cd railiance-cluster -
Prepare your config Edit ~/.railiance_gitea.conf with your Gitea URL, user, and token. (Never commit this file!)
-
Run bootstrap Use the playbooks in ansible/ to turn a bare Ubuntu server into a Kubernetes host.
-
Deploy services Install baseline services via Helm from the helm/ directory.
Incidents
Operations
- Deployment lifecycle
- Railiance app.toml contract
- Railiance overlay repo pattern
- Canary Helm template
- Stage 2 deploy and observe
- Promote, rollback, and onboarding
- Railiance run command
👥 Contributing
See CONTRIBUTING.md for rules, coding style, and workflow.
🌍 Vision
Railiance is more than infra scripts: it’s the foundation of self-empowering infrastructure, where humans and AI agents collaborate to manage systems with trust, clarity, and calmness.
From bare metal to resilient clusters, in one repo.