Open Source

Open Source

Public tools, configuration references, and code from the Reptile Industries internal toolchain. Built in the course of real operational work. Released because they are useful beyond it.

Infrastructure tooling Automation utilities Configuration templates More preparing

Public releases

Tools and utilities released from active Systems and Solutions work.

ri-infra-scaffold
Lightweight framework for defining and running operational automation tasks against self-hosted infrastructure. Minimal dependency philosophy — the scaffold should add less complexity than it removes.
Internal testing
Python · MIT
caddy-multisite-template
Production-tested Caddyfile template for multi-subdomain static site families with forward_auth integration. Covers TLS, compression, security headers, and protected route patterns.
Active
Config · MIT
backup-integrity-checker
Automated backup integrity verification tool. Validates backup completeness, tests restore paths, and produces human-readable reports. Designed for self-hosted environments without enterprise monitoring budgets.
Preparing
Python · MIT
documentation-standard
Proposed standard for infrastructure documentation designed for long-term human recoverability. Not just for the original operator — for anyone inheriting the environment years later.
Draft specification
Markdown · CC0

Configuration references

Hardened, production-tested configuration templates for common infrastructure components.

Caddy

Reverse proxy patterns

Multi-host static site routing, forward_auth integration, path-based access control, TLS override patterns, and compression configuration.

# forward_auth pattern
handle /client* {
  forward_auth ri-api:8787 {
    uri /api/auth/portal/verify
  }
  file_server
}
Docker

Self-hosted service patterns

Docker Compose patterns for self-hosted service stacks. Internal network isolation, volume management, and service dependency ordering.

# caddy-net pattern
networks:
  caddy-net:
    external: true

# Internal-only service
  expose: ["8787"]

Release philosophy

What gets released

Tooling with utility beyond the original operational context. We release when something is production-tested, documented, and maintainable by someone who was not involved in building it. Not before.

Releases come from Systems and Solutions work. Labs research that matures into tooling follows the same path.

Standards applied

  • Production-tested before release, not proof-of-concept
  • Full documentation for the intended use case
  • Minimal external dependencies by design
  • Licenced permissively where possible (MIT, CC0)
  • Maintained to a consistent standard after release

Related branches

Live

Systems

Where most of this tooling originates. Managed infrastructure, operational maintenance, and the environment that everything runs on.
Live

Solutions

Custom automation and software work. Some utilities released here originate in Solutions client work.
Research

Labs

Experimental tooling and early-stage research. When it matures and earns a release, it comes here.