Show newer

Here's what I got done this week:
* Debuted TinyPilot's new logo
* Added a 401(k) plan for TinyPilot fulfillment staff
* Built a homelab @TrueNAS server

Upgraded my homelab VM server to add in a 2 TB SSD and another 64 GB of RAM. New stats:

48 CPU cores
128 GB RAM

Here's what I got done this week:
* Launched TinyPilot Voyager 2
* Published my November retrospective
* Started experimenting with @ankiapp

I've been migrating services from GCP to Fly, and one of the features I missed from GCP was integrated logging from the web dashboard.

Today, Fly added integrated logging!
RT @flydotio
Just landed – view logs in your dashboard:

(@joao_lubien built this with ~180 lines of LiveView)

RT @tinypilotkvm
After months of hard work, we're happy to introduce the TinyPilot Voyager 2, our newest plug 'n play KVM over IP device with a cleaner and more compact form factor.

November was TinyPilot's highest revenue month ever. I saw a 62% sales increase just from removing a link. Plus, I reduced my Google Cloud Platform bill by 90% by switching to cloud providers that better meet the needs of small-scale services.

Everything else is working out great. Still love the case, still love Proxmox (enough that I purchased a license), still love doing development in VMs with VS Code + Remote SSH. Here's the full blog post

Show thread

1 TB of SSD was also a good choice, but I'm reaching the limit. I provision VMs with a 40 GB disk, but as I do more work in Docker, I find myself having to manually prune images too frequently. I purchased an additional 2 TB SSD, so now I'll have 3 TB total.

Show thread

64 GB of RAM was a good starting point, but I'm starting to reach the ceiling. I occasionally have to turn off VMs to free up RAM for a new system, and I'd rather just not worry about it. I ordered another 64 GB, since I left 4 RAM slots free in the original build.

Show thread

The dual Intel Xeon E5-2680 v3 CPUs ended up being WAY overkill. In over a year, I've rarely exceeded 50% CPU usage.

I'm tempted to just sell one of the CPUs since it seems like I only need one, but it feels sinful to run a dual CPU mobo with just one CPU.

Show thread

A reader emailed me asking if I'd change anything today about my 2020 homelab server build. It's worked great for me, but in retrospect, I definitely made some mistakes.

Here's my demo LogPaste GCR instance. Request flow:
1. HTTP request arrives
2. GCR launches LogPaste container
3. LogPaste loads DB from GCS
4. LogPaste serves HTTP request
5. GCR shuts down container after 10-90s
6. LogPaste saves data to GCS before exit

Show thread

LogPaste can now run on Google Cloud Run!

On GCR, you only pay for time LogPaste is serving requests. You don't have to manage external S3 credentials because it can write directly to GCS.

Big thanks to @steren on the GCR team for his help on this!

Here's what I got done this week:
* Continued ramping up for new product release
* Scrambled to resolve a part shortage
* Long vacation weekend improving @WhatGotDone

RT @czue
My November was just complete insanity.

In a 10-day period I:

- Broke my daily profit record 4 different times
- Was #1 on HN
- Made more than $30k

I’m still reeling. 🤯

On Plausible, the same operation takes 3 seconds, and most of that is just the time it takes me to click the menu.

Show thread

Compared with Plausible, Google Analytics is horrendously slow.

On GA, it takes 18 seconds to load the dashboard and pull up metrics for the previous month.

Show thread

I ran Plausible behind a proxy to reduce the chances of ad-blockers disabling it, so it's possible that 1/3 of my readers use ad-blockers that block Google Analytics.

I've since disabled the proxy and load Plausible normally. It felt user-hostile to fight with ad-blockers.

Show thread
Show older
Michael Lynch's Mastodon

Michael Lynch's personal Mastodon instance