π New blog post: π§ 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 PathNotesApacheHTTP8081https://localad.ddns.net/blogWordPress & CMS contentIPFSHTTP8080https://localad.ddns.net/ipfs/...Distributed file/web hostingNostrWebSocket7447wss://localad.ddns.net/nostrDecentralized communicationCaddyHTTPS443Front-end reverse proxySSL, redirects, clean routing
π¬ Comments (0)
Login to add a comment