InfraSync is my declarative infrastructure layer. I describe the target environment once and let Terraform provision it and Ansible converge configuration, so every machine I run the portfolio on comes up identically.
Part of my . Built on the "" model.
# 1. Clone
git clone https://github.com/Kimosabey/infrasync.git
cd infrasync
# 2. Install
# (see docs/GETTING_STARTED.md for the full setup)
# 3. Run
docker compose up- Single source of truth for infrastructure in version-controlled code
- Idempotent provisioning — re-running converges instead of duplicating
- Environment parity between my laptop and any private-cloud host
- Drift detection between declared and actual state
%%{init: {'theme':'base','themeVariables':{'primaryColor':'#ffffff','lineColor':'#2563eb','mainBkg':'#ffffff'}}}%%
graph LR
A([IaC Definitions])
B([Terraform Provision])
C([Ansible Configure])
D([Reproducible Environment])
A --> B
B --> C
C --> D
style A fill:#eff6ff,stroke:#2563eb,stroke-width:2px,color:#1e40af
style B fill:#eff6ff,stroke:#2563eb,stroke-width:2px,color:#1e40af
style C fill:#eff6ff,stroke:#2563eb,stroke-width:2px,color:#1e40af
style D fill:#eff6ff,stroke:#2563eb,stroke-width:2px,color:#1e40af
The interesting part is keeping declared state and real state reconciled — detecting drift and converging safely without tearing down running services.
See docs/ARCHITECTURE.md for the full HLD/LLD and design decisions.
| Layer | Technology | Role |
|---|---|---|
| Terraform | Terraform |
Infrastructure as code |
| Ansible | Ansible |
Configuration management |
| Docker | Docker |
Containerized local deployment |
- Architecture — high- and low-level design, decision log
- Getting Started — prerequisites, setup, environment
- Failure Scenarios — fault analysis and recovery
- Interview Q&A — deep-dive walkthrough
- Add a drift-report dashboard
- Wire secrets management
- Multi-host inventory support
Released under the MIT License.
Harshan Aiyappa Senior Full-Stack Hybrid AI Engineer Voice AI • Distributed Systems • Infrastructure