Update small_projects.yml

This commit is contained in:
akp 2025-04-13 22:48:56 +01:00
parent 27780010d2
commit 938a9fa3a2

View file

@ -1,3 +1,13 @@
- title: Setup a Windows mini-PC for photo editing
date: 2025-04-10
text: |
* Since I do a fair bit of [photography](/photography/), I end up needing to do a fair bit of photo editing too, which kinda sucks because of the state of creative software on Linux.
* Sorry GIMP, you're great but you just don't compare to professional tools.
* Since upgrading `wall-e` to a larger ThinkCentre, I've had a spare [ThinkCentre M73 Tiny](https://www.google.com/search?q=thinkcentre+m73+tiny&udm=2) kicking around. I nicked a 128GB SSD off of [Charlie](https://charliew.net/), installed Windows 11 on it (surprisingly without hitch, despite the machine being a 4th-gen i5 with no form of TPM whatever) and loaded VueScan and Affinity Photo onto it.
* The computer fits nicely on my existing desk by hiding under my laptop stand.
* This also helps get around its lack of WiFi card - I run it with it plugged into my laptop via ethernet. [NetworkManager is configured to share the laptop's WiFi connection over ethernet to the mini-PC](https://askubuntu.com/questions/169473/sharing-connection-to-other-pcs-via-wired-ethernet) and it might be one of my favourite uses of technology ever.
* I've since scanned and edited a whole roll of film on it, and while it's not the most performant thing in the world, the experience was immediately better than trying to do the same on Linux.
- title: Reworked small projects
date: 2025-04-09
text: |
@ -32,7 +42,7 @@
* Moved dependency management to `uv` and updated the Dockerfile to use that accordingly
* Replaced a very outdated dependency on `pyinotify` in favour of `inotify` (this stopped me upgrading past Python 3.11 because they removed an API `pynotify` needed in 3.12)
* Upgraded the generator's Python version to 3.14 (from 3.10 lol)
- title: Added a backlight block to cdmbar
date: 2025-03-05
text: |
@ -43,7 +53,7 @@
text: |
* [MusicBrainz](https://musicbrainz.org) is basically Wikipedia for music.
* As well as correcting some data for other albums, I created [a record for a new release I purchased](https://musicbrainz.org/release-group/b17a7b47-189d-4598-8c55-24ecd6f261a9)
- title: Setting up Navidrome and beginning to build out my music collection
date: 2025-02-21
text: |
@ -51,7 +61,7 @@
* I picked [Navidrome](https://navidrome.org) to manage that collection, and provide a nice API to use it on clients across my devices
* So far, so good! It's running on the newly-upgraded `wall-e` and I'm using [Copyparty](https://github.com/9001/copyparty) to upload files to be ingested into it along with [Feishin](https://github.com/jeffvli/feishin) and [Symfonium](https://www.symfonium.app/) as clients.
* Listening to lossless FLACs compared to mashed streaming audio is like being enveloped in a warm embrace of rich sound that you never realised you were missing
- title: Moving <code>wall-e</code> to new hardware
date: 2025-02-15
text: |
@ -72,11 +82,11 @@
text: |
* Historically, [Walrss](https://github.com/codemicro/walrss) has filtered feed items in the digests it generates using the time of each item, selecting only items that have been published since the last run.
* This is unreliable since feed items do not always have an accurate date or any date at all - instead, it's best to use the feed item ID to remember what has been seen before and only send the new stuff down the wire, which is what Walrss now does.
- title: Moving all my services to use Postfix as an MTA
date: 2025-02-09
text: |
* I run quite a few services that send email, each of which has historically been set up to reach out to SMTP services like Fastmail and Sendgrid to send their mail.
* This meant each service had its own API key and required a slightly annoying configuration process each time
* Each of my servers now runs an instance of [Postfix in a Docker](https://git.tdpain.net/pkg/docker-postfix) container that accepts incoming mail from other containers and forwards it on to Fastmail.
* Now, as opposed to having 8 different SMTP configurations littered about across multiple servers and email providers, I have 2 configurations, one per server, both pointing at Fastmail. Easy!
* Now, as opposed to having 8 different SMTP configurations littered about across multiple servers and email providers, I have 2 configurations, one per server, both pointing at Fastmail. Easy!