K3s and Longhorn I’ve long run a server (or servers) in my home. There’s been many different tech stacks used over the years, but I’ll save that saga for other posts. Today, without even providing the backstory for my current HomeLab adventures with K8s (Kubernetes), I’m going to dive into the specifics of a storage related problem and my quick and dirty solution. However, I suppose it’s at least important to know I’m running K3s, a lightweight Kubernetes distribution, and for my magical storage solution on Kubernetes, I’m running Longhorn.

The time has come to move to a new platform. Over the years, Wordpress (in various forms) has served reasonably well, but it is a constantly moving target. Since it is SO popular, it must constantly be upgraded, maintained, etc. Both security and performance are significant concerns. When I first started blogging, it seemed SO COOL to have a dynamic website. But in recent history, it’s just become a hassle.

In my ongoing adventures of playing with the Chromebox as a firewall, I eventually found a reason to use stock Ubuntu 16.04 instead of VyOS. For the most part, devices just work as you’d expect under Ubuntu. Even my USB ethernet network interface (NIC) devices work fine. But I eventually noticed a problem. By default USB NICs under Ubuntu 16.04 (which uses systemd & udev) are named “enxABCDEF123456” where ABCDEF123456 is the full MAC address of the device.

This is a bit of a follow up from my last post. I’ve still got my Asus Chromebox. I’m not running ESXi any more… but something I do want to try out is VyOS. Why? Well, my original intent when purchasing the Chromebox was to play around with it, but then I really did expect it to replace my home router. I’ve used pfSense for a long time, but I’m curious about VyOS because I know several people using EdgeRouter Lite which uses EdgeOS, a fork of VyOS.

I recently stumbled across the ASUS CHROMEBOX-M004U. It’s a Chromebox, which is cool in its own right, but I was interested in using it’s dual-core Celeron Haswell CPU, expandable RAM (up to 16GB), and M2 Sata storage for other purposes. First things first, you’ve got to enable the box to run things other than ChromeOS… Thankfully that’s well documented ( http://kodi.wiki/view/ASUS_Chromebox ), so I won’t go into detail at this time.

Today,IOS 7 dropped to the general public. As usually comes with the release, there was an Xcode update. I updated.  For some time, I’ve been using the git bundled in Xcode as it makes it simpler to get updates as they come with Xcode. Today, that yielded an amusing message. I use git via an alias in my .bashrc A simple version check reveals all:  git –version Oops… git is apparently subject to Apple’s licenses.

Cheesy post titles aside… I just discovered the very simple but incredibly useful RESTClient at: http://code.google.com/p/rest-client/ . It’s a simple Java GUI app for testing out one’s REST services. You can choose your: URL, HTTP method, add any custom headers, add a body for PUT/POST, set auth info, SSL info, and do simple scripting. This is an incredibly useful tool, AND a far cry better than doing it all on the command line with curl.

I’m taking time away from adding spit and polish to the exciting Here, File File project to say WOO HOO! The whole team (Adam, Buck, and I) are psyched! A few days ago we found out Here, File File is a finalist in the AppsFire Apps Star Awards. And today, The Unofficial Apple Weblog (TUAW) published a great HFF write up. If you haven’t seen our promo video yet, give it a whirl!

I’ve used the unix filesystem search utility find for many years. Though, like most things, until forced to learn its deeper secrets, I generally get by with only the most basic knowledge. One of the cool things about find is that you can specify a search and then execute an action on the results, all in one command. This example is probably my most common use of find: This means: find, in the current directory (.

I have an older G4 Mac Mini I use for testing the Mac app I’m working on (Here, File File F.K.A. Welcome to Your Mac. It’s just nice to have a machine that I can test both 10.4 and 10.5 as well as PowerPC compatibility. Yesterday I needed to do some updates on the 10.5 system and couldn’t remember my password. Google was my friend and showed me an Apple Knowledge Base article to solve the problem.