Cloudflare Warp is currently not supporting Linux. However, since it’s just Wireguard underneath, we can still use it unofficially. Install wgcf and wireguard-tools # Get wgcf from its repo. Install wireguard-tools. I use Manjaro so I will use pacman for this pacman -S wireguard-tools. Generate Wireguard config # You can now use wgcf to register, and then generate Wireguard config. wgcf register wgcf generate register command will create a file named wgcf-account.

An extremely fast streaming SAX parser for Node.js, written in C++

Breaking changes in camaro v6: require Node 12 or newer. Major performance improvement.

How to migrate from Zsh to Fish shell

kubectl run generators removed from kubectl 1.18, except one for generating pod.

A step by step guide on how to use Synology NFS as external storage with Kubernetes

We had an EC2 instance retirement notice email from AWS. It was our Kubernetes master node. I thought to myself: we can simply just terminate and launch a new instance. I’ve done it many times. It’s no big deal. However, this time, when our infra engineer did that, we were greeted with this error when trying to access our cluster. Unable to connect to the server: EOF All the apps are still fine.

The end goal is to be able to expose apps deployed locally on homelab publicly. I don’t want to expose multiple ports to the Internet for several reasons: I have to create multiple port-forwarding rules. The address not memorable because I need to remember the ports. Eg: homeip.example.com:32400 for Plex, homeip.example.com:1194 for VPN, and so on… The alternative is to use reverse proxy. setup reverse proxy setup port forward (80 & 443) for reverse proxy config reverse proxy to proxy the local apps Reverse proxy # I would have gone with nginx but I want to tinker with Caddy.

Everything you should know before buying your first homelab rack.

Currently, I’m working on building my homelab. It’s still a very much work in progress but everything is coming along nicely. I plan to host lots of stuff in my homelab and be able to access it while I’m not at home. I don’t feel comfortable exposing them all to the Internet so VPN to the rescue. The setup is straight forward. It’s different, depends on your lab equipment but the steps are always the same.