coulomb/railiance-cluster
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
railiance-cluster/docs
History
tegwick 9c55dfb02a RAIL-BS-WP-0008/0009: operator deploy + admin-sync smoke tooling 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-02 10:44:06 +02:00
..
incidents feat(pgpool): implement WP-0003 T01-T04 — permanent fix for pgpool-password bug 2026-03-10 14:16:22 +01:00
app-toml-contract.md Add Railiance promote rollback tooling 2026-06-27 17:01:11 +02:00
backup-restore.md feat(safety-net): create WP-0004, update preflight for OAS 5-repo layout 2026-03-10 15:21:29 +01:00
canary-helm-template.md Add Railiance canary chart template 2026-06-27 16:38:00 +02:00
CONTRIBUTING.md docs: add contributor guidelines 2025-09-12 02:25:53 +02:00
deployment-lifecycle.md Add Railiance promote rollback tooling 2026-06-27 17:01:11 +02:00
first_host.md feat(boundary): remove OS-hardening overlap; add k3s baseline workplan 2026-03-09 19:53:22 +01:00
kubeconfig.md feat(k3s-baseline): complete WP-0002 T01-T05 2026-03-10 09:43:16 +00:00
OODA.md railiance: initial bootstrap scaffold 2025-09-12 01:46:14 +02:00
operator-runbook.md RAIL-BS-WP-0008/0009: operator deploy + admin-sync smoke tooling 2026-07-02 10:44:06 +02:00
overlay-repo-pattern.md Add Railiance canary chart template 2026-06-27 16:38:00 +02:00
promote-rollback-onboarding.md Add Railiance promote rollback tooling 2026-06-27 17:01:11 +02:00
railiance-run-command.md Add Railiance Stage 1 run command 2026-06-27 16:24:17 +02:00
README.md Add Railiance promote rollback tooling 2026-06-27 17:01:11 +02:00
stage2-deploy-observe.md Add Railiance Stage 2 deploy observe tooling 2026-06-27 16:51:02 +02:00

README.md

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

  1. Convention over configuration
    Opinionated defaults remove friction.

  2. Don’t repeat yourself (DRY)
    Single source of truth in Git, reused everywhere.

  3. Automated OODA

    • Observe: collect telemetry.
    • Orient: AI interprets state.
    • Decide: human reviews & authorizes.
    • Act: automation applies changes.

  4. Self-Reliance
    Everything can be rebuilt from scratch, with no external dependencies beyond Git + credentials.

  5. Calm Ops
    Systems should be simple, resilient, and predictable.

📂 Repo Layout

  • ansible/ — bootstrap playbooks (OS setup, k3s install, etc.)
  • helm/ — Helm charts for services
  • k8s/ — raw manifests & overlays
  • tests/ — automated validation of infra steps
  • docs/ — documentation & contributor guides
  • tools/ — helper scripts (e.g. repo bootstrap)

🛠 Getting Started

  1. Clone the repo

    git clone <your-gitea-url>/railiance-cluster.git
cd railiance-cluster

  2. Prepare your config Edit ~/.railiance_gitea.conf with your Gitea URL, user, and token. (Never commit this file!)

  3. Run bootstrap Use the playbooks in ansible/ to turn a bare Ubuntu server into a Kubernetes host.

  4. Deploy services Install baseline services via Helm from the helm/ directory.

Incidents

Operations

👥 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.