🧠 Local Self-Hosted Stack: Decentralized, Resilient, and Future-Ready

✅ Purpose of the Project

This project is a deliberate build-out of a local server stack that combines:

  • Traditional Web Hosting (WordPress via Apache)
  • Decentralized Hosting (IPFS via Kubo)
  • Peer-to-Peer Communication (Nostr-compatible relay setup)
  • Smart Proxy Routing & SSL (via Caddy)

The goal is to explore self-sovereign web infrastructure — hosting websites, media, and apps entirely from local hardware, with cloud fallbacks only if needed. This is not just a tech exercise — it’s a strategic shift toward independence, privacy, and long-term sustainability.


🧰 What We’ve Done So Far

🖥️ 1. Set Up the Local Server (Ubuntu)

  • Installed Ubuntu Server on a secondary drive, bypassing consumer OS limitations.
  • Added a GUI to support hybrid CLI + desktop workflows.
  • Installed NVIDIA CUDA/NVENC stack for future GPU-based tasks (e.g. AI, video).

🌐 2. Restored Internet Access & SSH Control

  • Debugged network interface issues (static IP, DNS).
  • Confirmed remote access via SSH for headless administration.

🧪 3. Installed and Verified Core Systems

  • ✅ Apache (WordPress-ready, port 80)
  • ✅ IPFS / Kubo (Web3 hosting stack, port 8080)
  • ✅ Caddy (to become reverse proxy and certificate manager)

🌍 4. Linked to Public Internet (No-IP)

  • Registered public hostname: localad.ddns.net
  • Verified dynamic DNS updates via cron or router
  • Confirmed remote visibility (open port scan, IPFS gateway test)

🛣️ Where We’re Going

🎯 Final Architecture Overview

ServiceProtocolPortPublic PathNotes
ApacheHTTP8081https://localad.ddns.net/blogWordPress & CMS content
IPFSHTTP8080https://localad.ddns.net/ipfs/...Distributed file/web hosting
NostrWebSocket7447wss://localad.ddns.net/nostrDecentralized communication
CaddyHTTPS443Front-end reverse proxySSL, redirects, clean routing

Similar Posts