Multi-Host Docker Infrastructure Stacks

Problem

Self-hosted services across different machines become difficult to reproduce when configuration, host constraints, and secret handling are undocumented. This repository organizes independent Compose stacks and records where each workload runs.

Deployment Model

Operating Rules

• Every stack can be started or stopped without changing unrelated services.
• Real secrets stay in local .env files; the repository contains only safe examples.
• Images used on the OCI host must support linux/arm64.
• Long-running services use an unless-stopped restart policy.
• Host documentation records active, legacy, stopped, and inactive workloads.

Maintained Workloads

The repository includes a consolidated OCI remote-access stack, Karakeep, database services, and historical configurations for services such as n8n, Vikunja, Redis, and Nginx. Status is documented rather than presenting every checked-in stack as production-active.

Current Status

The repository is actively maintained. Configuration and host documentation are available in docker-rahul on GitHub.