Nick Bodmer

As Built: The Homelab That Runs This Site

Sat, 18 Jul 2026 00:00:00 GMT

Notes to future me: what this site runs on, how the pieces fit, and the two things I'll actually need later — how to change this site, and how to stand up a new one.

The stack

Hardware: an Intel NUC running Proxmox
Platform: Coolify in a VM on that Proxmox host
Each site: a Docker container — a multi-stage build (a Node image builds the Astro site, an nginx image serves the static files) — built and run by Coolify from a GitHub repo
Ingress: a Cloudflare Tunnel into Coolify's built-in Traefik proxy
DNS + TLS: Cloudflare (nameservers, proxied records, edge certificates)
Deploys: git push plus one Coolify API call

No ports are forwarded on the router. Nothing in the homelab is reachable from the internet except through the tunnel.

How it was built

Two Claude sessions did the work:

Claude (design) — I wrote a brief: the mission statement, the pages I wanted, real content, and hard constraints (system fonts, one accent color, light + dark, vanilla CSS). It produced a design system as CSS tokens plus HTML mockups of every page. That handoff is committed in the repo under design/.
Claude Code — translated the design into an Astro static site, migrated every old post (Hugo + micro.blog) into src/content/posts/, and wired up the deploy. I made the decisions; it did the typing.

Source is public: github.com/ampsonic/nickbodmer.com.

How Cloudflare routes a request

DNS for the domain lives at Cloudflare, proxied (orange cloud).
A Cloudflare Tunnel links my network to Cloudflare. The cloudflared connector dials out, so there's no inbound hole into the homelab.
In the tunnel's public hostname routes, the domain points at Coolify's Traefik proxy on the LAN.
Traefik reads the Host header and hands the request to the right site's container. Every site shares the one tunnel and the one proxy; the hostname is what separates them.
TLS is terminated at Cloudflare's edge, so the internal hop is plain HTTP. Always Use HTTPS is on, and www is a proxied CNAME with a redirect rule to the apex.

Because Traefik routes by hostname, I can test any site from the LAN before its DNS exists — just send the request to Coolify with the right Host header.

Changing this site

Everything lives in a local checkout of the repo.

New post: add a .md (or .mdx for a YouTube embed) to src/content/posts/. Frontmatter needs title and date; set draft: false when it's ready.
Preview locally: npm run dev, or npm run build && npm run preview for the real static output.
Ship it: npm run deploy.

npm run deploy pushes to GitHub and then calls Coolify's deploy API directly. A plain git push won't deploy on its own: Coolify isn't exposed to the internet, so GitHub's webhook can't reach it — the script is what tells Coolify to rebuild. (The API token lives in .env.deploy, gitignored — single-quote it, the token contains a |.)

Standing up a new site

The repeatable version of what I just did:

Build it — Claude Code, into a GitHub repo. Include the Dockerfile + nginx.conf from this repo (styled 404, gzip, cached assets).
Cloudflare zone — point the domain's nameservers at Cloudflare.
Coolify — new app from the repo → Build Pack: Dockerfile → expose port 80 → set the domain → deploy.
Tunnel route — add a public hostname for the new domain, pointing at Coolify's Traefik. Same tunnel, same proxy; Traefik sorts it out by Host.
Polish — turn on Always Use HTTPS; add a www CNAME and a WWW→root redirect if wanted.
One-command deploys — copy scripts/deploy.sh and the .env.deploy pattern, set the new app's UUID (from its Coolify URL) and an API token.

That's the whole machine. Future me: if a deploy doesn't show up, it's almost always the webhook — just run npm run deploy.

Taming the Home Lab: Friendly Local Domains with UniFi + Pi‑hole + NPM

Sat, 28 Jun 2025 00:00:00 GMT

Last week I finally hit my breaking point with URLs like http://192.168.1.10:32400. Sure, I can remember that Plex runs on port 32400… but what about Home Assistant? Or my random test container from three months ago? My brain already holds enough useless trivia—memorizing port numbers doesn’t need to be part of the collection.

I wanted a clean, memorable way to reach every self‑hosted service on my network—plex.home.arpa, pihole.home.arpa, npm.home.arpa, you name it.

First stop: Nginx Proxy Manager (NPM). It’s the brains that maps each friendly hostname to the right internal port so I never type :32400 again.

The snag: my UniFi Cloud Gateway Fiber can’t point a wildcard domain (*.home.arpa) straight at the NPM container, so NPM alone didn’t get me there.

Enter Pi‑hole. By taking over DNS, Pi‑hole answers every *.home.arpa query with the IP of my Mac mini—the box where NPM is listening. UniFi forwards DNS to Pi‑hole, Pi‑hole hands out the single IP, and NPM does the port‑mapping magic. Two tools, one neat solution.

Side note: All my containers run inside OrbStack using docker compose. HTTP‑only for simplicity – I’m keeping everything on plain HTTP inside the LAN.

Below is the final setup, why I chose each piece, and enough breadcrumbs for Future Me (and maybe Present You) to recreate it without the usual home‑lab tinkering.

Why I bothered

Human‑friendly URLs – I can type “plex” instead of an IP:port combo.
Single entry point – NPM puts every service behind one memorable domain.
Ad‑blocking for free – If Pi‑hole is already answering DNS, why not?
One place to grow – Adding a new service is a 10‑second NPM host rule.

Gear & high‑level layout

Box	Role	Key Detail
UniFi Cloud Gateway Fiber (UCG)	Router / DHCP	Hands out itself (`192.168.1.1`) as DNS
Mac mini (192.168.1.10)	Docker host	Runs Pi‑hole + NPM + everything else

DNS path in one breath: Client → UCG → Pi‑hole → wildcard → NPM → internal service.

Step‑by‑step

1. Deploy Pi‑hole & Nginx Proxy Manager containers

Spin up both services using OrbStack + docker compose (or your container runtime of choice).

Pi‑hole defaults to port 80 for its admin UI, but that clashes with NPM’s reverse‑proxy listener, so I remapped Pi‑hole’s web interface to port 82 in my docker‑compose.yml.

The only ports you need exposed are:

Pi‑hole: 53/udp + 53/tcp (DNS) and 82/tcp (web UI)
NPM: 80/tcp (reverse proxy) and 81/tcp (admin UI)

That’s it—we’ll skip the YAML here to keep things short.

2. Point the UCG at Pi‑hole

Settings → Internet → DNS

Primary: 192.168.1.10 (Pi‑hole)

Secondary: (leave blank)

I originally tried adding Cloudflare (1.1.1.1) as a backup so the household would stay online if the Mac mini went down. Bad idea. UniFi doesn’t strictly prefer the primary resolver—it will query the secondary even when the primary is healthy. Each time that happened Cloudflare returned NXDOMAIN for my internal hosts, the gateway cached the negative answer, and local lookups failed until I rebooted the gateway.

Settings → Network → LAN → DNS Mode: Auto

DHCP keeps handing out 192.168.1.1 to clients. Behind the scenes, the gateway forwards everything to Pi‑hole, so if Pi‑hole ever goes down the network still feels alive.

3. Add a wildcard override in Pi‑hole

In the Pi‑hole Admin UI, go to Settings → All Settings → Miscellaneous → misc.dnsmasq_lines and paste:

address=/.home.arpa/192.168.1.10

Click Save & Restart DNS. From now on, every *.home.arpa hostname resolves to the Mac mini.

4. Create proxy hosts in NPM

Inside the NPM admin UI (http://192.168.1.10:81), add a Proxy Host for each service:


Domain	Forward To
`plex.home.arpa`	`http://192.168.1.10:32400`
`npm.home.arpa`	`http://192.168.1.10:81`
`pihole.home.arpa`	`http://192.168.1.10:82`

Because we’re sticking with HTTP internally, there’s no SSL checkbox to worry about. It Just Works.

Open the browser—no ports, no IPs, just plex.home.arpa. Victory.

TL;DR Config Recap

Clients            → DNS 192.168.1.1 (UCG)
UCG (forward DNS)  → 192.168.1.10 (Pi‑hole)
Pi‑hole wildcard   → *.home.arpa → 192.168.1.10
NPM port 80        → Reverse‑proxy to service ports

Simple, memorable hostnames and one less mental lookup table.

Future Nick, if you’re troubleshooting this at 2 a.m., you’re welcome.

Spacial Vision Livestream - The Talk Show: Live from WWDC 2024

Wed, 12 Jun 2024 00:00:00 GMT

Last night, I watched the entirety of The Talk Show Live from my Vision Pro, and it was an incredible experience. As always, the show was top-notch; I loved hearing the Apple team speak with such passion about their work.

The common narrative that Apple is lagging in AI seems misguided. The sophisticated privacy initiative involving private cloud computing appears to be the result of years of development. Considering the complexity and potential costs, a subscription component for AI services wouldn’t surprise me in the future.

Streaming the show in spatial vision was fantastic. Using Sandwich’s Theater app, the virtual screen displayed a smaller rectangle, making the on-stage presenters appear life-sized rather than disproportionately large. This setup created the illusion of sitting in the front row and added to the intimacy of the event. It was a significant improvement over the YouTube replays I’ve watched previously. The combination of stereo video and the knowledge that it was live heightened the experience, making me wish for live sports broadcasts on Vision Pro.

Although there were some framerate hiccups, the minimal movement on stage meant they didn’t detract from the overall experience much. It’s a minor issue that can be improved.

The audio seemed to be in stereo rather than surround. While there was plenty of audience interaction, the sound came solely from in front of me. It would have been amazing to hear cheers and applause from behind, enhancing the feeling of being seated in the front row. The video was limited to a rectangle in front of me. Being able to look around and see the audience would have made the experience even more immersive, truly replicating the feeling of attending the event in person.

Overall, participating in the show was an amazing experience. Kudos to the teams at SpacialGen, Sandwich, and, of course, John Gruber. It sounds like everyone was holding their breath, hoping it would all work out, and it truly did!

MagBak RimCase for Model 3 Uberturbine Quick Review

Tue, 05 Sep 2023 00:00:00 GMT

I love my Tesla Model 3 Performance, but I have found the wheels incredibly easy to damage against curbs.

Ouch

I ordered a set of the new RimCase covers for these wheels, and I have to say I’m pretty impressed. They cover the existing damage perfectly, and unless you examine the wheels closely, I don’t think you can even tell that they are there. I ordered it with a set of “spares”, so if I do some more damage, I can just replace a single section.

Installation wasn’t difficult, but it was a bit time-consuming. MagBak includes a plastic film that goes on each spoke and around each edge, which took some time to install. I’d say the total install was 10-15 minutes per wheel.

In the end, I think they look great. I do wonder if there will be any issues when I need to get new tires, I hope I don’t have to remove and reinstall them.

RimBak installed

My helper

Tue, 05 Sep 2023 00:00:00 GMT

Today, I was installing a few outlets that have built-in USB-C ports. I was having trouble identifying the correct breaker, so I had a Zoom meeting between myself and this lamp I plugged in.

Replacing the battery in the Eufy Spaceview Pro baby monitor

Mon, 14 Aug 2023 00:00:00 GMT

We really like our Eufy Spaceview Pro baby monitor (Model 8321-M). We’ve had this one for a few years, and the battery life has slowly drained to the point that it shuts off immediately when you unplug it.

About six months ago, I used the trick found on Reddit where you unplug the battery for about 30 seconds and plug it back in. This seemed to give it some additional life, but now the battery is dead. (Not surprising after two years of daily full charge/discharge cycles).

In this video I open up the monitor, remove the old battery and replace it with a new one.

Links:

Amazon Page for the Eufy Spaceview Pro

Amazon Page for the battery pack

Reddit Discussion of unplugging the battery for extra life

SwiftData errors in Xcode 15 Beta 6: Type 'PropertyOptions' has no member 'cascade'

Thu, 10 Aug 2023 00:00:00 GMT

EDIT: As of XCode Beta 7, you need to add the default value back in.

Original Post:

I upgraded to Xcode 15 Beta 6, and found some new errors in my SwiftData Project.

On my @Relationship macros, using .cascade, I now have the error “Type ‘PropertyOptions’ has no member ‘cascade’”

We need to add deleteRule: .cascade instead.

But now we see a new error. “Variable ‘self._$backingData’ used before being initialized”

We can no longer set default values where we declare the variables. Removing the = [] takes care of the error. (And I did not need to add it to the initializer.)

Final, working code:

Deploying your app on-device after becoming a paid Apple Developer

Sun, 09 Jul 2023 00:00:00 GMT

I’ve been working on an app, and as a ‘free’ Apple Developer, I’ve just been running my app on-device. This leaves the app on my phone for a few days, but you are quickly hit with this error:

"App Name" is no longer available.

Since my app was starting to come along, I decided it was time to pay the $99 fee and become a full Apple Developer. Took a few days after submiting my application, but soon enough I was approved.

I continued working on my app, and was surprised to quickly run into the same error message. I thought that becoming a paid developer would “automatically” fix this, but there’s a process to deploying your app on a device for testing.

I found my way to the Distributing your app to registered devices guide.

It breaks down into a few steps:

Collect Device identifier
Register device on the Apple Developer website
Update Provisioning profile
Archive the app
Export the app
Install app on the device

To make matters easier, some of these steps were already completed.

My device identifier was already registered (perhaps because the device is tied to my apple id already?)

No provisioning profile was needed, as by default, you get “automatic signing”.

Steps needed

Archive and distribute:

Product > Archive
Distribute App > Ad hoc

Ad hoc distribution options: keep defaults
Automatically manage signing
Export to a location on disk.

When you save the exported app, Xcode creates a folder that contains a few files, including the iOS App file, which is a file with an .ipa filename extension. Distribute that file to your users so they can install it on their devices by using Xcode or Apple Configurator 2.

Window > Devices and Simulator
Select your iOS device
Click the + icon under "installed apps" (even if your app is already listed)
Select the .ipa file that you exported earlier.
Done!

Should I wait for SwiftData?

Mon, 03 Jul 2023 00:00:00 GMT

I’m working on an app idea, and the newest features of iOS 17 seem like they will make my life a lot easier, especially SwiftData. Is it a bad idea to start using these features knowing I’ll need to limit the app to iOS 17? I think not, but I’m not sure.

Sun, 28 May 2023 00:00:00 GMT

Busy day.

Photochromic Sunglasses: Generic vs Transitions XTRActive

Wed, 17 May 2023 00:00:00 GMT

I have been buying all my prescription glasses at eyebuydirect.com for years, and about a year ago, I decided to try their “photochromatic” lenses. These are glasses that are clear indoors, but when you are outside, they darken automatically to become sunglasses.

Eyebuydirect offers multiple options for photochromic lens upgrades:

‘Generic’ Photochromic - ~$36
Transitions Signature - ~$100
Transitions XTRActive: ~$140

My first pair was the generic photochromic lenses, and they worked really well. I had only two complaints: They did not get dark in the car (the UV-blocking glass of the car prevents it from changing), and they were slow to ‘transition’ back to clear when you walked indoors after being outside.

I broke the frame of those glasses and when reordering, decided to give the “Transitions XTRActive” a try. The eyebuydirect website says this about Transitions XTRActive:

Transitions® XTRActive® lenses deliver the best extra darkness and the best extra light protection indoors & outdoors. They’re clear indoors with a hint of protective tint and darken outdoors, even in the car. They also block 100% UVA/UVB and filter harmful blue light indoors & outdoors.

I was really excited to have them work in the car! However, real-life results haven’t been that impressive. They darken a bit in the car, but not to “full sunglasses” darkness. Also, they have a slight tint all the time. The description sort of points this out, but I didn’t understand that fully until I got them.

My recommendation, skip the Transitions branded stuff; the generic photochromic for $36 bucks is a great deal.

Which Mac Desktop should I buy?

Wed, 17 May 2023 00:00:00 GMT

For the past few weeks, I’ve been debating between a Mac Mini with M2 Pro or a Mac Studio with M1 Max. I eventually decided on the M2 Pro with 16GB of RAM and 512GB of storage. It felt like the right balance for me - I know 16GB has been enough on my M1 MacBook Air, and maxing out the CPU performance has been my only issue. However, 512GB of storage is more than enough for me now. I’ll add an external SSD to keep my entire iCloud Photo Library locally.

I’m confident this Mac Mini with M2 Pro will last me a couple of years, and if the M3 makes a big difference when it comes out, I can always look at the Mac Studio. But for now, this feels like the right decision!

I decided to buy the base Mac Mini with M2 Pro (16GB, 512GB), after waffling between a spec’d up version and a Mac Studio. Here’s my reasoning:

16GB has been just fine on my M1 MBA
Maxing out the CPU has been the only issue I’ve had
I’m using less than 512TB currently, and switching to a desktop means I can very easily add a 2TB SSD. Finally, I can keep my entire iCloud photo library locally.

Now I’ll feel fine for the next year or two, and if the M3 with the process shrink makes a big difference, I can look at a Mac Studio or something.

When it comes to choosing the best computer for my needs, I recently decided to purchase an Apple Mac Mini with the M2 Pro processor (16GB, 512GB).

This was not an easy decision to make, as I had to consider my current computing needs as well as my future needs. The choice was ultimately between purchasing the specced-up version of the Mac Mini, or going for a Mac Studio. After a lot of thought, I decided on the Mac Mini. Here’s why:

Firstly, currently I own an M1 Macbook Air and with 16GB of RAM, I feel that I have enough memory to comfortably work with. While I have experienced some slowdowns and lags at times, it has been due to the processor, not the RAM.

Secondly, I currently only use 512 GB of storage, meaning that I do not need a bigger storage capacity as I do not store too much data. Once I switch to a desktop computer, I can easily add in a 2TB SSD, and this will be perfectly suitable for me. I love being able to keep my entire iCloud photo library stored locally.

Finally, I am confident that the Mac Mini M2 Pro will serve me well for the next couple of years. I believe that the M2 Pro is the perfect processor for my needs, and I do not need to worry about upgrading straight away. If in the future the Mac Mini M3 and its process shrink makes a difference, then I can look into buying a Mac Studio or something else.

All things considered, I am really happy with my decision to go for the Mac Mini M2 Pro. It has all the features I need and I am confident that it will provide me with the computing power I need for the foreseeable future. I am looking forward to seeing the amazing things I can do with the Mac Mini.

Synology Replication with ZeroTier

Sun, 18 Apr 2021 00:00:00 GMT

Introduction

What I want is to backup my Synology NAS without huge cloud storage costs. In a perfect world, I'd take a 2nd Synology, drop it off at a friend's house, and it would just work. No messing with their network, setting up dynamic dns services, static IP addresses or port forwarding. Just plug it in and turn it on, and it works. And it's possible using a service called ZeroTier. Using ZeroTier, the two devices will appear to be on the same local network, no matter where they are in the world.

Watch on YouTube

Instructions

Primary NAS uses a static IP on local network
Remote NAS set to DHCP
Create Zero Tier Account
Create Network
Download correct ZeroTier package for your synology models
- Architecture per Synology model: https://github.com/SynoCommunity/spksrc/wiki/Architecture-per-Synology-model
- Zerotier Synology download: https://download.zerotier.com/dist/synology/
On Primary NAS
- Package center > manual install > select ZeroTier package
- Launch ZeroTier, add network ID
- Approve device from ZeroTier dashboard
- Label Device Name
Repeat for Remote NAS
On Primary and Remote NAS
- Package manager > search snapshot > install "snapshot replication"
On Primary NAS
- Open snapshot replication
- Replication > create
- Select remote, next
- Server name: use zerotier IP of Secondary NAS
- Advanced Settings
  - Source Server
  - Server name or IP address drop down, select zerotier IP, click OK
- Enter Secondary NAS username / password, click next
- Select destination volume
- Select share to replicate
- Send initial copy over the network
- Select replication schedule
- Set retention schedule
- Apply
- Done!

Links

https://github.com/SynoCommunity/spksrc/wiki/Architecture-per-Synology-model https://download.zerotier.com/dist/synology/

iRacing

Sat, 09 May 2020 00:00:00 GMT

I've recently fallen in love with a racing simulator called iRacing. I already had a wheel and pedal tucked away in a closet, so I pulled them out and set up iRacing with my Oculus Rift. What a blast! I love the competitive nature and the ability to work to slowly raise my skill level.

I quickly found that I didn't like having to attach and detach the racing wheel to my desk, so I picked up the Playseat Challenge, which is a folding chair designed just for racing. It makes it very simple to setup for racing and tear down when I'm done.

Here's a quick video I put together after one of my Rookie Mazda Global Cup races.

Watch on YouTube

Install youtube-dl with homebrew for Mac

Mon, 23 Dec 2019 00:00:00 GMT

Here is a short tutorial video on how to install youtube-dl via homebrew for Mac.

Watch on YouTube

Setting up a website with Ansible

Sun, 15 Dec 2019 00:00:00 GMT

Create VPS

Create a new VPS (virtual private server), I chose to host my VPS on DigitalOcean. I've already uploaded my Mac's public key to DigitalOcean, so it is installed automatically. This will allow ansible to connect without a password.

The ansible and config files I use are at the bottom of this post.

Initial config

ansible-playbook initial_server_setup.yml -i hosts -l nickbodmer.com -u root

This initial configuration playbook will:

create 'wheel' group (which probably already exists)
enable passwordless sudo
create my user 'nick' with sudo privileges
add my ssh key to that new user
disable password authentication for root
update apt
install a few packages, most importantly UFW firewall
allow SSH through the firewall
enable the firewall

nginx setup

ansible-playbook -i hosts -l nickbodmer.com nginx.yml

This playbook will:

Install and start nginx
open ports 80 and 443 for http and https
copy the nginx config file to the server
symlink the config file to sites-enabled
restart nginx

At this point we have a fully running http webserver.

letsencrypt using certbot

certbot will automatically configure nginx to use https and set a cron job to automatically renew your certificates.

Add certbot repository:

sudo add-apt-repository ppa:certbot/certbot

Install certbot for nginx:

sudo apt install python-certbot-nginx

Install cert for domain:

sudo certbot --nginx -d nickbodmer.com -d www.nickbodmer.com

Files needed

hosts

[cloud]
nickbodmer.com

[cloud:vars]
ansible_python_interpreter=/usr/bin/python3

[local]
192.168.1.206

initial_server_setup.yml

###########################################################################################################
# DO Community Playbooks
# Playbook: Initial Server Setup
# Based on: https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-18-04
# Dedicated Guide: https://www.digitalocean.com/community/tutorials/automating-initial-server-setup-with-ansible
###################################################################################################################

---
- hosts: all
  remote_user: root
  gather_facts: false
  vars:
    create_user: nick
    copy_local_key: "{{ lookup('file', lookup('env','HOME') + '/.ssh/id_rsa.pub') }}"
    sys_packages: [ 'curl', 'vim', 'git', 'ufw']

  tasks:
    - name: Make sure we have a 'wheel' group
      group:
        name: wheel
        state: present

    - name: Allow 'wheel' group to have passwordless sudo
      lineinfile:
        path: /etc/sudoers
        state: present
        regexp: '^%wheel'
        line: '%wheel ALL=(ALL) NOPASSWD: ALL'
        validate: '/usr/sbin/visudo -cf %s'

    - name: Create a new regular user with sudo privileges
      user:
        name: "{{ create_user }}"
        state: present
        groups: wheel
        append: true
        create_home: true
        shell: /bin/bash

    - name: Set authorized key for remote user
      authorized_key:
        user: "{{ create_user }}"
        state: present
        key: "{{ copy_local_key }}"

    - name: Disable password authentication for root
      lineinfile:
        path: /etc/ssh/sshd_config
        state: present
        regexp: '^#?PermitRootLogin'
        line: 'PermitRootLogin prohibit-password'

    - name: Update apt
      apt: update_cache=yes

    - name: Install required system packages
      apt: name={{ sys_packages }} state=latest

    - name: UFW - Allow SSH connections
      ufw:
        rule: allow
        name: OpenSSH

    - name: UFW - Deny all other incoming traffic by default
      ufw:
        state: enabled
        policy: deny
        direction: incoming

nginx_config.cfg

server {
       listen 80;
       listen [::]:80;

       server_name nickbodmer.com www.nickbodmer.com;

       root /home/nick/nickbodmer.com/;
       index index.html;

       location / {
               try_files $uri $uri/ =404;
       }
}

nginx.yml

---
- hosts: all
  tasks:
    - name: ensure nginx is at the latest version
      apt: name=nginx state=latest
      become: yes
    - name: start nginx
      service:
          name: nginx
          state: started
      become: yes
    - name: UFW - Allow http/https connections
      ufw:
        rule: allow
        name: 'Nginx Full'
      become: yes
    - name: copy the nginx config file and restart nginx
      copy:
        src: /Users/nick/Google Drive/Sync/Documents/Ansible/nginx_config.cfg
        dest: /etc/nginx/sites-available/nginx_config.cfg
      become: yes
    - name: create symlink
      file:
        src: /etc/nginx/sites-available/nginx_config.cfg
        dest: /etc/nginx/sites-enabled/default
        state: link
      become: yes
    - name: restart nginx
      service:
        name: nginx
        state: restarted
      become: yes

Thu, 19 Apr 2018 00:00:00 GMT

Unboxed a new Benq 4K HDR monitor!

How to Shuck the WD RED drive from an Easystore

Mon, 07 Aug 2017 00:00:00 GMT

A tutorial video I created on how to remove the internal hard drives from the Western Digital Easystore external hard drive. These are often found for a much lower price than you would pay for the internal drive by itself.

I have four of these drives in my Synology NAS, and they work great.

Watch on YouTube