TIL.cafe

Learning FreeBSD, read Absolute FreeBSD book

2026-01-01T00:00:00+00:00

I decided to start learning FreeBSD... even though I'm already running MacOS, Linux & Windows at home.

why learn FreeBSD?</h2>
A whole mix of reasons.

I want more deterministic computing in my life. More stability, less enshittification of services.</li>
Keep looking wistfully at retro computing and solarpunk and offline first computing... want things more like that.</li>
I'm personally finding the Linux world a bit overwhelming these days. So many different ways to install software, seems like distributions are increasingly diverging from each other. Also, it seems like design priorities seem to favor interactive/desktop usage over headless/server usage. This is great for desktop usage! But it sure seems to lead to a lot of different ways to install software on a machine.</li>
I'm want to put my limited learning time into skills I think will last. And I think FreeBSD related skills will be relevant for a long time.</li>
I've heard good things about ZFS and jails and want some personal experience.</li>
A friend of mine has been using FreeBSD for years and has offered to help when I get stuck. :)</li> </ul>
So... giving it a go. Should help build broader and deeper experience if nothing else.
what & how</h2>
My initial goals: use at home for self hosting needs - running web apps, file servers, hosting storage/backups, etc.
I've been enjoying technical books a lot more over the last few years, so I want to start with a good overview from a book so I don't miss fundamental stuff. Based on several recommendations, decided to read Absolute FreeBSD 3rd edition</a>. The author recommends</a> buying this book from no starch press directly (and has a coupon code in that FAQ).
how's that going so far?</h2>
Great!
I've just finished reading Absolute FreeBSD and have installed FreeBSD on two machines and fought with DNS (turns out modern caching DNS resolvers fail if the machine clock is too far off... because TLS (I should write a TIL about that)).
Overall it feels... both nostalgic and futuristic. Things just feel familiar already. I guess that's because so many of the abstractions I'm familiar with from other OSs are from BSD and Unix in general. So... kind of retro... but also very much now. It supports USB, NVMe, EFI, lots of modern hardware, etc. It somehow tickles my retro-computing itch while being useful for everyday work.
A few things I really like so far:

Consistency. Once you learn a pattern it appears over and over.</li>
Separation of default config from local config, making it easier and safer to upgrade. And sample files (`something.conf</code> is often paired with a something.conf.sample</code> containing a default or example configuration).</li>`
`Docs! Love the culture of documentation. Man pages actually seem to exist for everything... and they're useful! I'm having to retrain my myself to look at local docs before jumping to the web.</li>`
`Self contained. The system is a complete unit. Can learn from the docs... which are ...on the computer! Feels wild these days... so used to everything being online... and maybe not even on the web anymore, maybe in a transient chatroom.</li>`
`Jails and VMs built-in, ZFS feels like virtualized storage (in a good way!) on every machine.</li> </ul>`about Absolute FreeBSD, the book</h2> Overall Absolute FreeBSD</a> is a gem and I highly recommend it. Written by a real human with real experience. It shows and is much appreciated. The author often highlights a few specific features or config options which are either widely useful or easy to miss.</li> That said... the author definitely has a bit of a BOFH</a> vibe... which will likely be fun for some folks and rub others a bit the wrong way. It's mostly kept to footnotes, so you can skip it.</li> To the above note... the writing has a specific person's voice, which I appreciate these days!</li> It hits a great balance between overview and details. I feel like I got a solid tour of the space, shown a few key things that would be easy to miss and have a solid base to dig into the project docs.</li> </ul> Absolute FreeBSD was published six years ago... in 2019. Six years is a long time in tech... but in this case it's still very relevant and useful. The fundamentals of FreeBSD don't appear to have changed much in that time. In my mind this is a very good thing. Successfully learning fundamentals from a six year old book supports the idea that I'll be able to use this knowledge for many years to come. Specifically, the book talks about FreeBSD features through version 12, and version 15 was released a month ago. I did a skim through release announcements and it looks like the main updates since 12 are: Many version updates of dependencies and subsystems.</li> All supported architectures built with LLVM/clang instead of gcc.</li> Code moved from SVN to Git.</li> arm64 now Tier-1 platform.</li> nfs servers can run in vnet jail (and pnfs support).</li> Renamed blacklistd</code> --> blocklistd</code> (yea! Reading "blacklist" in 2025 felt really jarring).</li> New method for updating the base system (freebsd_update</code> --> pkg</code>).</li> </ul> So... the only part of the book that's out of date is the section on upgrading the base system. Nice! next</h2> Next I'm planning to iterate a bit on exsiting services I have at home (file server, backups, network config, etc) and start adding a few more self hosted things (code repos, photos, music) and try to learn more about ZFS and jails along the way.

Book: 50 Years of Text Games 2025-10-23T00:00:00+00:00 I finished reading 50 Years of Text Games</a> recently. It's amazing. If you have any interest in text, stories, or games, I highly recommend it. I've been slowly working through it a few chapters at a time over many months. Savoring it. The structure is inspired: deep dive on one game per year, 50 games, 50 years. Each chapter is an essay, both about the specific game and the context and times surrounding it. It works really well. I now have a much better understanding of the history of text games as a whole and mental model of many specific games. Also ended up with a list of them that I want to try at some point. Whee! I've been alive and using computers for most of that time period... and it's amazing to follow along chapter by chapter... how it sometimes connects to existing experiences (I ran a BBS with one of the door games covered in the book) or fills in blanks that I missed along the way. Some chapters were deeply nostalgic, while others covered games and kinds of games completely new to me. Really enjoyed that contrast. Would love to read similar books on other topics! Does this remind you of anything? If so, please let me know! Hosting a static web site using Google Cloud Run 2024-04-30T00:00:00+00:00 context</h1> This website (https://til.cafe/</a>) is currently a static site, hosted on Google Cloud Run. Wait... isn't that a serverless container hosting service? Yes. You may be asking why I'm hosting a static site on something designed for running containers? The details are in this post about the tradeoffs</a>. The short version is that it works really well (no fiddling), and can be set up to automatically build. So I can edit text, check it in, push and the site gets updated. Nice. So... how fiddly is it to set up? Not bad. And that's what the rest of this article is about. overview</h1> OK, so Cloud Run is a service that hosts containers that serve web content. You can host pretty much any application written in any you'd like, as long as you can wrap it in a container and it responds to HTTP requests. A static website is made from a bunch of files (at least HTML/CSS, probably more) on disk somewhere that can be accessed via HTTP. So... how do we connect these two? Files can't serve themselves, so we need a web server, and then wrap it and the files into a container and send that to Cloud run. We only need two short config files to do this... but it was a bit fiddly to get there, so let's walk through the details. static website files</h2> I kinda skimmed it above... but while you could write the HTML/CSS directly (and there are pretty good arguments for doing it), this site uses a Static Site Generator</a> - software which takes text files of some kind and produces the HTML files. I'm currently using Zola</a>, but for this article, it doesn't matter, anything which will produce the files works. In my case they're generated by running this command: $ zola build </code></pre> So, where you see that below, replace it with whatever you use to generate the files. web server</h2> Next, we need to actually serve those files over HTTP. Nginx & Apache are currently the most popular web servers... but for this I wanted something as easy as possible to configure with minimal dependencies (to keep the container size small). At some point, I ran across Caddy</a>, and while their marketing page is kinda over-the-top, it ships as a single file binary and the config is very clean: :8080 { root * /srv file_server log { output stdout format json } } </code></pre> This says: Listen on port 8080, using the file_server module to serve all files in /srv</code> and log to stdout</code> in JSON. Some notes: 8080</code>: Cloud Run expects a process listening on 0.0.0.0 (all IPs) and port 8080 by default (see: Container runtime contract</a>). So I just hard-coded it here. If you need the port to be variable, check out Caddy placeholders</a></li> format json</code>: This is neat because Cloud Run automatically forwards stdout to Cloud Logging and it parses JSON formatted logs into structured logs you can query and filter.</li> </ul> Dockerfile</h2> The next step is to build a container. I'm using a two-stage Docker build</a>, a neat pattern I learned from Daniel Azuma's post "Deploying My Blog to Google Cloud Run"</a> First we build the static website (using Zola, in my case) and since we only want the website in the final image, we start a new image (using a pre-made Caddy image) and copy the config and web site files to it. FROM alpine AS build RUN apk add zola WORKDIR /workspace COPY . /workspace RUN zola build #### FROM caddy:2.7-alpine COPY --from=build /workspace/Caddyfile /etc/caddy/Caddyfile COPY --from=build /workspace/public /srv </code></pre> build and deploy an image to Cloud Run</h2> And... now we need to actually get this online. How do we get this on Cloud Run? Luckily Cloud Run can handle things from here. Well... I have to admit that I'm assuming that the website is stored in source control. I hope yours is? Please say yes. The source for this website (til.cafe) is here</a>. Cloud Run can be configured to build an image and deploy that whenever a git repository changes. It supports repositories hosted by a few different services, GitHub</del> Codeberg (see update</a> below) in this case. In case things change, I'm going to refer to the official docs for setting up continuous deployment</a> I followed those steps, giving a service account permission to connect to GitHub, choosing the trigger (push to the main branch, in my case), and choosing Dockerfile</code> as the build type. Since it only needs to be done once on a personal project, I did it via the web UI, but you can set things up manually</a>. Update from the future: I'm now deploying using gcloud run deploy</code> from my local machine. Details in update</a> below. </blockquote> usage</h1> All of the above is one-time set up. In everyday usage, I edit the files for my site, test the changes locally, check them into main, and push them to GitHub. A few minutes later, the new version is online! This works from whatever tools I use to update the git repo... so it works from desktop, laptop, mobile, whatever. I'm really happy with this pattern. I haven't had to touch it once since setting it up over a year ago. note about branches</h2> Reading this carefully has probably made some of you nervous... Isn't this deploying to production on every change? Yes, pretty much, at least everything that lands on main will get deployed. This is a small personal site, so I have it configured to build and deploy on every push to main. That probably wouldn't make sense for anything more critical than a personal blog or anything with multiple developers. You can also trigger builds on pushes to specific branches or tags as well as pull requests. And you can setup different Cloud Run services at subdomains for each, so it's straightforward to create an integration environment separate from production, for example. Not every push needs to go to prod. ;) enjoy</h1> Happy static site hosting! 2025-09 update - moved source to Codeberg</h1> As of September of 2025, I've moved most of my code hosting to Codeberg.org</a>. Cloud Run doesn't currently support deployment hooks from Codeberg and I've started wanting to push commits more often than I update the site... so... I'm now doing deployments manually from my local machine. This is the key command: $ gcloud run deploy til-cafe --allow-unauthenticated --max-instances=2 \ --region=us-west1 --project=til-cafe --source . </code></pre> (note that last period, it's telling --source</code> to use source code from the local directory) The full command I'm using also has a call to Jujutsu</a> to append the latest commit hash to the Cloud Run revision for reproducibility. You can see the full command in the justfile</code> in the til.cafe</a> source repository. Also, there is a slight variation to push to a separate staging site. I also ended up creating a .gcloudignore</code> file (patterned after .gitignore</code> syntax) which gcloud run deploy</code> uses to exclude some files from upload. 'fq' is 'jq' for binary formats 2024-03-15T00:00:00+00:00 Just started playing with fq</code> a "jq for binary files": https://github.com/wader/fq/</a> (jq</code></a> is a command line tool for parsing and manipulating JSON documents) It's a command line tool for exploring, visualizing and parsing binary files. Initial impression is really positive. Look at this lovely breakdown of the details of a WAVE file. Like most tools it doesn't parse most metadata chunks, but it gives a really clear view of the structure of the chunks in a file, and at least which chunks are in a file. Google Cloud static site hosting options 2024-02-26T00:00:00+00:00 Like a lot of folks recently, I finally decided to setup a personal website/blog. You're reading it now! :) This post covers different options for hosting a static site on Google Cloud and what I decided in the end. Teaser: I picked something that isn't usually considered for static sites and I'm really happy with how it worked out. Why bother hosting your own blog?</h2> I'll quote Scott Hanselman here: I would encourage you all to blog more. Tweet less. Blogs are owned by you. They are easily found, easily linked to, and great conversations happen with great blog posts. The river of social media rushes on and those conversations are long forgotten. A great blog post is forever. "Your Blog is the Engine of Community"</a> -- Scott Hanselman </blockquote> Also, I'm inspired by folks like Julia Evans</a> and Simon Willison</a> who learn in public and share what they've learned as they go. I want to do more learning in public and ... because I know myself... I need make that as easy as possible or I will get distracted troubleshooting shiny tech stuff. Goals / Constraints</h2> Context always matters. Here are some goals and constraints I had in mind while making this decision, so you can see how they map to yours. hosted on Google Cloud It's the environment I know best. (I work there).</li> text file based authoring, stored in a version control system I'm a software developer and want to use tools I'm familiar with.</li> low administration overhead, hopefully zero maintenance I've done a lot of infrastructure work so it's really easy to spend time fiddling with stuff instead of writing words. Writing words is hard. The more reliable things are, the less time I'll spend fiddling with software instead of writing words.</li> easy site updates It should be as easy as possible to update the site once I'm OK with the writing.</li> static site (mostly) Static sites are just a set of files, which should help simplify all of the above goals. But... I will likely want to add a few interactive bits someday... so "mostly".</li> </ul> Solutions Considered & Tradeoffs</h2> Here are the options I considered and their tradeoffs (for this goal). Google Cloud Storage</h3> Cloud Storage</a> is my favorite Google Cloud Service. There, I said it. Sorry, other services. You give it a file and a name, it keeps it for you. When you give it the name later, it gives you the file again. That's the contract. It's very reliable. Cloud Storage is designed for 99.999999999% (11 9's) annual durability</a>. It's fast and affordable. It's also... a bit fiddly when used for direct web hosting. It can do it, and there are solutions for most things you probably want to do... but it's fiddly</a>. I was also a bit worried about things getting out of sync as I add and remove files over time. gsutil rsync</code> would solve that... but I'm still diffing a collection of files for each deployment, I'd love atomic deployments and rollbacks. The big bummer for my use-case is that you can't directly serve HTTPS traffic via a custom domain without paying a time-based (rather than usage based) fee for a load balancer. Drat. If you'd like to try it out, this is a nice tutorial exploring static sites on Cloud Storage</a> </blockquote> Firebase Hosting</h3> Well, why not Firebase Hosting</a> then? It's pretty much Cloud Storage underneath with a UX focused on hosting websites. Plus a CDN (content delivery network... local cached copies of the site for people around the world), neat! It handles HTTPS for custom domains, and has lots of options for previewing sites, integrating Cloud Functions, Cloud Run, GitHub integration, it can "...rewrite URLs for client-side routing, set up custom headers, and even serve localized content." and, more. It's awesome. As someone new to it, though... it also seemed like... maybe more than I need for a small site. And even though their developer tooling UX is excellent... there are still a lot of features to think about. Try it out: Getting started with Firebase</a> tutorial. </blockquote> Google Cloud Run</h3> "Google Cloud Run</a> is a managed compute platform that lets you run containers..." ... so... why am I looking at a container hosting platform for my static site? Well... partly because I'm a programmer and I'm just sure I'll want some kind of dynamic content at some point. Yes... even when trying to keep things simple, I can't help myself. But keeping things to static site hosting... It handles HTTPS certificate generation and termination. Scaling up and (especially important for this blog) down to zero. Containers are designed for encapsulation, so I get atomic deployments and rollbacks. You can point Cloud Run at a GitHub repository and it will automatically build and deploy a new version of the site after every push to a branch. Neat. This seemed like a complexity sweetspot for me. Several Cloud Run quickstart tutorials</a> </blockquote> Decision</h2> After a bit of research and fiddling, I ended up with a nice pattern for deploying a static site to Cloud Run. The core idea is wrapping the static site data up together with a single file webserver into a docker image. With a couple of small config files checked into the repository, it will build the site HTML/JS/CSS, wrap it and the webserver into a container image and deploy it. On every push to the repository. Now that it's all set up, I edit text files and preview locally, then push when I'm ready to publish. Everything after that happens automatically. I've been running it this way for over a year, and haven't had to think about it or troubleshoot anything. I consider that a win! (for this kind of site! :) ) In a future post, I'll walk through the details of setting it up. (Update: details post is here</a>). In the mean time, you can check out the source here</a>. In particular, the Dockerfile</code> and Caddyfile</code> are all that's needed to host the output of pretty much any static site generator via Cloud Run. 12-bit rainbow palette from Kate Morley 2024-01-26T00:00:00+00:00 Kate Morley has published a 12-bit color palette</a>, made of "...twelve colours chosen with consideration for how we perceive luminance, chroma, and hue." I really like it, and I wanted to document it here so I don't lose track of it. Example from her site: Check out the details and design notes: https://iamkate.com/data/12-bit-rainbow/</a> Convert GIFs to black and white using gifsicle 2023-07-29T00:00:00+00:00 If you need to convert a GIF image from color or grey scale into just black and white, here is a recipe using a command line tool called gifsicle</a> Here is my original image (captured from the Playdate Simulator</a> included in the Playdate SDK). And after running this command: gifsicle --gamma=1 --use-colormap=bw < rain.gif > rain_bw.gif </code></pre> We get a black and white image. I needed to use the gamma flag for this image, since it's so low contrast, the default result was a solid black image. And... that's pretty much it. For more details on various options for gifsicle</code>, see the gifsicle docs</a> To go the other direction, we need a custom color map in the gifsicle format. Here is an example of one in the Playdate Simulator color scheme: Contents of pd_colors.txt</code>: 50 47 40 177 174 167 </code></pre> And then pass that into the --color-map</code> flag: gifsicle --gamma=1 --use-colormap=pd_colors.txt <rain_bw.gif > rain_pd.gif </code></pre> Backyard Rain Soundscape app for Playdate 2023-07-23T00:00:00+00:00 I've published a rain soundscape listing app for Playdate</a> handhelds. Demo: </iframe> More information and download: Backyard Rain Soundscape</a></iframe> Playdate development is easy and fun 2023-07-07T00:00:00+00:00 I recently got a quirky little handheld gaming device, called Playdate</a>. I had a fantastic early experience developing for it. It's gotten me more excited about programming than anything else in years. And... I don't understand exactly why. This is my attempt to think it through. A Playdate gaming handheld. So small! This was one of those supplychain delayed orders, so I'd mostly forgotten about it by the time it arrived. And while I was planning to use it for distraction gaming, I'm somehow finding myself developing software for it! I had no plans to make any games... but somehow the developer experience is so good, that I've almost accidentally started, and can't seem to stop now! This post is about the initial dev experience and how great it is. The first evening I played with it, I posted this</a>: "Super impressed with the #playdate SDK. I'm a programer, but I've never done game dev. Had an idea for a... well more of a fidget toy than a game. An hour later and it's running on the physical device. Was able to merge two of the examples and find a few additional functions to call from the docs and ... done!?! The Playdate devs have done really nice work. Docs are good, tooling is good, everything worked. Stellar first impression!" </blockquote> the story</h2> Let's walk through that in more detail. I got the device during a work week, fiddled with a few games and set it aside. A few evenings later, I thought... "They have development tools for it, right? I wonder if I could make a logo spin?" </blockquote> Not sure why I was thinking about that exactly, but... I decided to try. Opened the Playdate developer site</a> and it looks like they have three options: Lua and C APIs with a local simulator, and an online authoring tool called Pulp</a>. I decided to go with Lua, since I've been meaning to learn it to script other software. Downloaded the SDK, installed, and poked around at the examples. Created a folder with a copy of PlaydateSDK/Examples/Game Template</code> and that seemed to run. Started reading the reference docs</a>, which are quite clear and to-the-point. After getting that first thing running in the simulator, I spent about 45 minutes reading docs, poking at examples and searching the developer forums</a>. I'm recreating this from memory, but I think these are the main sources I used: PlaydateSDK/Examples/Single File Examples/crank.lua</code></li> https://devforum.play.date/t/basic-crank-rotate-sprite/8422</a></li> </ul> Combine those into one program... and... with that, I had everything I needed. "It's working?!?" </blockquote> Not what I expected. I'm used to long research side quests and yak-shaving. I got something working on the device in an hour? This is fun. OK, and the crank on the side just feels good. I have to admit that I did spend the next two hours fiddling with image dithering (for the 1-bit actually-only-black-and-white screen) and fiddling with crank response timing, adding additional button handlers, etc. thoughts</h2> OK, but... why was this so much easier to get started and more fun than I expected? After thinking about it and talking it over with colleages for a few days... I think... it's not magic, the Panic folks have done all the fundamentals really well. Things that worked well for me (first time Playdate developer): I could choose between multiple tools which support different levels of abstraction and programming experience.</li> The simualator works well and allows quick iterations.</li> The reference docs</a> are accurate, comprehensive, concise and ... crucially: all in one place. I just scrolled up and down the same page with an occasional search-in-page.</li> The developer forums</a> are full of useful posts.</li> Constraints simplify. The device and APIs are very focused. It think it could be possible to... just learn them all. Most dev tools feel like they're growing faster than I can keep up.</li> Seeing something you just made on a physical device in your hand just feels good.</li> I'm of an age where 1-bit visuals are super nostalgic, so I'm sure that helps.</li> And maybe most of all: fast feedback loops. In Lua at least, pretty much everything I tried just worked or failed right away. Edit, save, view, repeat. Once things are working well enough, it only takes 15-20 seconds to get that build from the simulator to the physical device.</li> </ul> your turn</h2> I want everyone to experience this! ... but... today at least, they're backordered for many months. That said, the local dev tools</a> and Pulp</a> (online authoring tool) are free and work without a device. Consider playing around with them. If you're at all curious (and can afford to), order one and forget about it until it arrives. Your future self will thank you. RPN calculator tutorial 2023-03-18T00:00:00+00:00 RPN Tutorial, incl. some things HP did not tell</a> RPN: Reverse Polish Notation. Or postfix notation or stack logic, the calculator logic system used in many Hewlett-Packard (HP) calculators. I'd heard of and slightly poked at RPN calculators a few times in the past. Not sure why, but I gave them another look recently and this tutoral made them finally click for me. It's very good. If you've ever been curious about RPN or HP calculators, give it a look. It also includes links to many simulators. Also useful if you're an RPN person trying to get someone else into them. :) About 2023-01-31T00:00:00+00:00 TIL = Today I Learned</h1> Hi! I'm Brian Dorsey... and this is my website. Imagine a relaxed cafe where folks are hanging out, working on projects and sharing what they've learned recently. This site is where I'm sharing public notes, things I've learned recently, project updates, etc. Hopefully you find some of it helpful and use it to do something important to you. Take care, -Brian Nerd Font patcher on MacOS 2023-01-14T00:00:00+00:00 "Nerd Fonts</a> patches developer targeted fonts with a high number of glyphs (icons). Specifically to add a high number of extra glyphs from popular ‘iconic fonts’ such as Font Awesome, Devicons, Octicons, and others." Nerd Fonts looks like a very nice way to get a lot of extra visuals at the command line, lots of programming related icons and shapes. They even have downloads of popular programming fonts patched with the extra icons. So if you use one of them, head to https://www.nerdfonts.com/</a>, download their patched version and you're good to go. However, I've recently switched to a paid programming font (Berkely Mono</a>, it's lovely) and as you'd expect for a paid font, it's not included. Luckily, the Nerd Font folks have a patcher</a>! I got a bit confused about how to run it on MacOS, but once it all came together, it worked great. Here's what worked for me, as of 2023-01-14: I'm on MacOS, and use homebrew</a>, so: $ brew install fontforge </code></pre> Then go to https://www.nerdfonts.com/</a>, scroll to the bottom and download FontPatcher.zip, and unzip that somehwere temporarily. I also copied the font I wanted to patch into that same directory. $ fontforge -script ./font-patcher --complete BerkeleyMono-Regular.otf </code></pre> The script created a new (much larger) font named Berkeley Mono Regular Nerd Font Complete.otf</code>. I copied that to /Users/USER/Library/Fonts/</code> (where USER is my local username) and updated my terminal program's config to use this. Done! Now I can experiment with some of the recent command line tools which use these icons, like lsd</a> (ls</code> replacement), Zellij</a> (like tmux/screen), and Starship</a> (fancy shell prompt). Interview with Richard Hipp: Story of SQLite 2023-01-02T00:00:00+00:00 CORECURSIVE #066 The Untold Story of SQLite With Richard Hipp</a> This interview gives a lot of context on where SQLite came from, and how it grew to be the project it is now. SQLite has a somewhat different approach to software compared to many other open source projects, (few dependencies, lot's of testing, small core team), and it's been quite effective. Use iOS and Git? Check out Working Copy 2022-12-27T00:00:00+00:00 If you use git and have an iOS device, check it out: https://workingcopy.app</a> It works on both phones and iPads, has an embedded editor and supports several methods of integrations with other applications. I've mostly used it for small updates, but it seems to have enough features to support even complex workflows. Kroki creates diagrams from textual descriptions 2022-12-26T00:00:00+00:00 Kroki</a> is an API and interactive web site which creates diagrams from text. Hello World! 2022-12-25T00:00:00+00:00 Hello World!

enjoy</h1>
Happy static site hosting!</p>

Solutions Considered & Tradeoffs</h2>
Here are the options I considered and their tradeoffs (for this goal).</p>

TIL.cafe

Learning FreeBSD, read Absolute FreeBSD book

next</h2>
Next I'm planning to iterate a bit on exsiting services I have at home (file server, backups, network config, etc) and start adding a few more self hosted things (code repos, photos, music) and try to learn more about ZFS and jails along the way.</p>

Book: 50 Years of Text Games

Hosting a static web site using Google Cloud Run

'fq' is 'jq' for binary formats

Google Cloud static site hosting options

12-bit rainbow palette from Kate Morley

Convert GIFs to black and white using gifsicle

Backyard Rain Soundscape app for Playdate

Playdate development is easy and fun

RPN calculator tutorial

About

Nerd Font patcher on MacOS

Interview with Richard Hipp: Story of SQLite

Use iOS and Git? Check out Working Copy

Kroki creates diagrams from textual descriptions

Hello World!

TIL.cafe

Learning FreeBSD, read Absolute FreeBSD book

next</h2> Next I'm planning to iterate a bit on exsiting services I have at home (file server, backups, network config, etc) and start adding a few more self hosted things (code repos, photos, music) and try to learn more about ZFS and jails along the way.</p>

Book: 50 Years of Text Games

Hosting a static web site using Google Cloud Run

Dockerfile</h2> The next step is to build a container.</p>

enjoy</h1> Happy static site hosting!</p>

'fq' is 'jq' for binary formats

Google Cloud static site hosting options

Why bother hosting your own blog?</h2> I'll quote Scott Hanselman here:</p>

Solutions Considered & Tradeoffs</h2> Here are the options I considered and their tradeoffs (for this goal).</p>

12-bit rainbow palette from Kate Morley

Convert GIFs to black and white using gifsicle

Backyard Rain Soundscape app for Playdate

Playdate development is easy and fun

the story</h2> Let's walk through that in more detail. I got the device during a work week, fiddled with a few games and set it aside. A few evenings later, I thought...</p> "They have development tools for it, right? I wonder if I could make a logo spin?"</p> </blockquote>

RPN calculator tutorial

About

Nerd Font patcher on MacOS

Interview with Richard Hipp: Story of SQLite

Use iOS and Git? Check out Working Copy

Kroki creates diagrams from textual descriptions

Hello World!

next</h2>
Next I'm planning to iterate a bit on exsiting services I have at home (file server, backups, network config, etc) and start adding a few more self hosted things (code repos, photos, music) and try to learn more about ZFS and jails along the way.</p>

enjoy</h1>
Happy static site hosting!</p>

Solutions Considered & Tradeoffs</h2>
Here are the options I considered and their tradeoffs (for this goal).</p>