[Homelab Notes] Old Laptop Repurposing Plan: Building a 24/7 Dan Home Cloud v1 Self-Hosted Server

Sitting at home was a 6-year-old unused laptop. Recently, I decided to repurpose it—wiping the original Windows OS and converting it into a 24/7 low-power home cloud server (Dan Home Cloud v1). Based on power consumption estimates, with the screen off and maintaining low-to-medium loads, total monthly electricity usage comes to only ~7–14 kWh, translating to around NT$20–50 (~$0.60–$1.50 USD) per month. The cost-efficiency is exceptionally high.

Architectural Shift: From "Personal Computer" to "Server"¶

Transforming a retired laptop into legitimate infrastructure relies on maximizing resources and operating in Headless mode:

Completely stripping GUI overhead: The default Windows OS consumed 2GB–4GB RAM at idle. I reinstalled the machine with a CLI-only Ubuntu Server 24.04 LTS, which idling uses only ~500MB RAM. This leaves the remaining ~11.5GB of RAM and CPU horsepower dedicated entirely to containerized services.

Decoupling Control: Static IP and SSH Remote Management¶

A server shouldn't rely on external monitors or keyboards. To achieve full remote operations, I established network and management anchors:

Static IP Anchoring: Managed via Netplan, I assigned a static internal IP to the network adapter (enx...), ensuring it retains the exact same address post-reboot without DHCP variance.
Headless SSH Management: Once configured, peripheral cables were disconnected, and the laptop was tucked away in a well-ventilated corner. I simply SSH into the server via Terminal on my primary workstation for full system management.

Containerization & Observability: Docker + Portainer¶

To prevent套件 version conflicts ("Dependency Hell"), all applications are managed as Docker containers:

Infrastructure as Code (IaC): Maintained in a Git repository containing docker-compose.yml files, completely decoupling hardware from application services. If hardware fails in the future, running docker-compose up on a new host restores services in seconds.
Separation of Concerns & Observability: The underlying Linux system manages OS security and permissions, while Portainer is deployed as a visual dashboard for monitoring container health and real-time logs.

Mapping Homelab to Cloud Architecture¶

Beyond practical home utility, this deployment maps directly to cloud architecture concepts from a Solution Architect's perspective:

Ubuntu Server Laptop $\rightarrow$ AWS EC2 Virtual Instance
Netplan Static IP $\rightarrow$ AWS VPC & Elastic IP
Docker Containers $\rightarrow$ AWS ECS Container Service
Portainer Panel $\rightarrow$ AWS Management Console

Next Step: Living Room KTV Music Request System¶

With the underlying infrastructure ready, the first project queued for deployment is PiKaraoke containerized via Docker, paired with Cloudflare Tunnel for external domain routing. Family members at home or visiting can scan a QR code on their smartphones to search YouTube, queue songs, and adjust key signatures in real time for a complete self-hosted KTV experience!