🌐 Self-Healing Private Cloud Infrastructure

🚀 Converting Legacy Hardware into a Zero-Trust Resilient Lab

---

📖 Executive Summary

This project is a deep-dive into Platform Engineering and Cloud Infrastructure. I have converted a 10-year-old laptop into a fully functional, globally accessible, and self-healing private cloud. This lab serves as the foundation for my transition into MLOps and Solution Architecture.

"Turning 'E-Waste' into 'High-Performance Infrastructure'."

---

🛠 Tech Stack & Architecture

Layer	Technology Used
OS	(Optimized Linux)
Networking	(Encrypted Tunneling)
Automation	(Self-Healing Logic)
Storage
Communication	(E2EE Chat)

---

📂 Project Modules (Deep Dives)

🤖 Automation & Self-Healing

Problem: Service downtime and manual restarts. Solution: Custom Systemd units with Restart=always logic.

• Managed to achieve 99.9% uptime despite hardware reboots.
• Log analysis via journalctl for real-time debugging.

🔒 Zero-Trust Networking

Problem: ISP-level port blocking and SSL timeouts (502 Bad Gateway). Solution: Port-shifting and Tailscale Funneling.

• Internal Traffic: Port 8099 ➡️ Global Gateway: Port 10000.
• Implemented Encrypted Tunnels bypassing traditional risky Port Forwarding.

☁️ Private Cloud Storage

• Full-scale implementation of Nextcloud for decentralized data access.
• Integrated local drive mounts into a unified cloud interface.

💬 Matrix Secure Chat

• Deployed a decentralized communication server (Synapse).
• End-to-End Encryption (E2EE) for private team communication.

---

🛠 The Troubleshooting Diary (Engineering Mindset)

During this journey, I didn't just "install" apps; I solved real infrastructure problems:

1. The Database Lock Crisis: Identified SQLite deadlocks in the File Browser database. Solved using process-kill routines and state resets.
2. The Funnel Conflict: Debugged 502 Bad Gateway errors by analyzing Tailscale gateway logs and shifting traffic to Port 10000.
3. Hardware Constraints: Monitored system health using htop to ensure stable performance on legacy CPU/RAM.

---

📈 Roadmap: The Path to 2026-2035

• Phase 1: Bare-metal Linux & Service Automation. (Current)
• Phase 2: Containerization (Moving to Docker & Docker-Compose).
• Phase 3: Infrastructure as Code (Managing lab via Terraform).
• Phase 4: MLOps (Deploying and Scaling AI Models on this infrastructure).

---

🤝 Connect with Me

• GitHub: CodeWithPritom
• LinkedIn: [Your LinkedIn Profile]
• Focus: Cloud Support | Platform Engineering | MLOps

---

This lab is a living document. I update it as I break things and fix them again.