<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Wilbert Josh Alfornon</title>
    <description>The latest articles on DEV Community by Wilbert Josh Alfornon (@wbert).</description>
    <link>https://dev.to/wbert</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3418809%2F4fbb0e84-9017-40e1-a1cf-a4a2471d8ea1.jpg</url>
      <title>DEV Community: Wilbert Josh Alfornon</title>
      <link>https://dev.to/wbert</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/wbert"/>
    <language>en</language>
    <item>
      <title>My Home Lab Setup: From Zero to Self-Hosted</title>
      <dc:creator>Wilbert Josh Alfornon</dc:creator>
      <pubDate>Thu, 07 Aug 2025 17:05:21 +0000</pubDate>
      <link>https://dev.to/wbert/my-home-lab-setup-from-zero-to-self-hosted-278e</link>
      <guid>https://dev.to/wbert/my-home-lab-setup-from-zero-to-self-hosted-278e</guid>
      <description>&lt;p&gt;I wanted more control over my apps. So I built a home server—no cloud, no monthly fees, and no vendor lock-in. Here's how I did it step-by-step, what gear I used, and how you can replicate it with just a weekend and some old hardware.&lt;/p&gt;




&lt;h4&gt;
  
  
  Step 1: Buy a compact second-hand machine
&lt;/h4&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F8ln6i4hh1709y9yxas3k.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F8ln6i4hh1709y9yxas3k.jpg" alt="Step 1" width="800" height="600"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I wanted a server that runs 24/7 and uses low power. I saw a compact PC for sale on the second-hand market for only PHP 3,000, so I immediately bought it.&lt;/p&gt;

&lt;p&gt;Specs:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;2-core, 4-thread CPU&lt;/li&gt;
&lt;li&gt;8 GB RAM&lt;/li&gt;
&lt;li&gt;256 GB NVMe SSD&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It uses low power and runs 24/7 without issue. It’s enough for basic app hosting. Any unused laptop and or computer will do if it runs x64&lt;/p&gt;




&lt;h4&gt;
  
  
  Step 2: Install Ubuntu Server
&lt;/h4&gt;

&lt;p&gt;To install Ubuntu Server, I downloaded the ISO image from their official website and created a bootable USB using Rufus. After installing, I connected the server to my local network via LAN cable and accessed it using SSH from my main computer.&lt;/p&gt;

&lt;p&gt;Once installed, I SSH into it over the local network.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;ssh username@192.168.1.123&lt;/code&gt;&lt;/p&gt;




&lt;h4&gt;
  
  
  Step 3: Installing Docker, Docker Compose, Tmux, Nvim and Cloudflared
&lt;/h4&gt;

&lt;p&gt;Here is the architecture.&lt;br&gt;
&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F45qtanpxi86tui6y80se.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F45qtanpxi86tui6y80se.jpg" alt=" " width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Install essential packages:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;sudo apt update&lt;/code&gt;&lt;br&gt;
&lt;code&gt;sudo apt install tmux cloudflared docker neovim&lt;/code&gt; &lt;/p&gt;

&lt;p&gt;Follow Docker’s official guide if needed.&lt;/p&gt;




&lt;h4&gt;
  
  
  Step 4: Pull and build projects
&lt;/h4&gt;

&lt;p&gt;I Cloned my own project from GitHub.&lt;/p&gt;

&lt;p&gt;Use Docker Compose to build and run it on the server.&lt;/p&gt;

&lt;p&gt;CI/CD is not set up yet. You test by accessing the local IP and port.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F6g55arz39bphjfi881vq.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F6g55arz39bphjfi881vq.jpg" alt="System Monitor" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If it loads on the LAN, it’s ready for the web.&lt;/p&gt;




&lt;h4&gt;
  
  
  Step 5: Set up Cloudflare Tunnel
&lt;/h4&gt;

&lt;p&gt;I bought a domain name for around PHP 140 for a year. Then, I installed Cloudflared, which allows me to expose my local server securely without port forwarding.&lt;/p&gt;

&lt;p&gt;I pointed the DNS nameservers to Cloudflare’s, and after some propagation, it was ready.&lt;/p&gt;

&lt;p&gt;Cloudflare now handles:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;DNS records&lt;/li&gt;
&lt;li&gt;SSL cert issuance&lt;/li&gt;
&lt;li&gt;Tunnel security&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Start tunnel setup:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;cloudflared login&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Open the auth link, log in, and wait for the pem key to appear.&lt;/p&gt;

&lt;p&gt;Create a tunnel:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;cloudflared tunnel create tunnel&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Edit the config: &lt;code&gt;~/.cloudflared/config.yml&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;&lt;code&gt;nvim ~/.cloudflared/config.yml&lt;/code&gt; or &lt;code&gt;nano ~/.cloudflared/config.yml&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Example config:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F6r2tim697hf0qqvn6b6q.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F6r2tim697hf0qqvn6b6q.png" alt="Tunnel Setup" width="800" height="467"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Route the tunnel to your domain:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;cloudflared tunnel route dns my-tunnel sys-mon.wbert.xyz&lt;/code&gt;&lt;/p&gt;




&lt;h4&gt;
  
  
  Step 6: Run the tunnel
&lt;/h4&gt;

&lt;p&gt;Use tmux to keep it alive in the background:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;tmux new -s tunnel&lt;/code&gt;&lt;br&gt;
&lt;code&gt;cloudflared tunnel run tunnel&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Detach with &lt;code&gt;Ctrl+B&lt;/code&gt; then &lt;code&gt;D&lt;/code&gt;.&lt;br&gt;
Or, if you prefer, you can set it up as a service:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;sudo cloudflared servers install&lt;/code&gt;&lt;br&gt;
`&lt;/p&gt;




&lt;h4&gt;
  
  
  Final Thoughts
&lt;/h4&gt;

&lt;p&gt;I now have a server running my personal projects with custom domains and HTTPS — all self-hosted and secure, without needing to expose my network to the internet directly. It’s satisfying and gives me full control over my setup.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>devops</category>
      <category>programming</category>
      <category>linux</category>
    </item>
  </channel>
</rss>
