Homelab Adventures

Sign in Subscribe

Topic

homelab

A collection of 18 issues

Re-thinking the Homelab Setup

The setup as described in the prior posts has actually served me well for the year or so it was running. During that time, though, I kept noticing things that bothered me, some to a larger extent than others. In no particular order, I found troubling that: * Using OCI images

Document Sharing - Nextcloud + Collabora Code

With the media server more or less wrapped up (we'll probably revisit that for improvements down the line), another thing we may want to accomplish is become independent of Google Drive and the Google office applications (or OneDrive and Office 365). To that end, we'll deploy

Media Server, Pt 6 - Jellyfin

Probably should have pushed this earlier - Jellyfin is the actual core of the media server part of this. It's the server that users actually connect to in order to watch movies or TV shows; it has some limited capability to serve e-books and music as well, so

Media Server, Pt 5 - Transmission

Like Sabnzbd, Transmission is a downloader - this one, for Torrents. The basic steps for installation of a new container should be pretty evident by now: Create the storage directories, add to the compose file, although now that we have Authentik installed, there's another step, at least for

Dogfooding it, Pt 7 - Authentik

I was trying to avoid this. Getting into authentication is a rabbit hole. For the moment, I am choosing Authentik because it is reasonably easy to configure, and supports the features I want. For a good start, Authentik uses Redis / Valkey as memory cache. So, we'll need to

Media Server, Pt 3 - VPN

Entire books have been written about this. I'm not going to repeat them here, no go into all the various arguments to be had. The fact of the matter is, though, sometimes, for whatever reason, you don't want people to be able to easily track online

Media Server, Pt 2 - Directory Structure

The various components making up a media server by necessity interact. There'll be PVR applications to manage movies, serialized shows, music, and electronic books; downloaders to obtain content - only that my dear readers are licensed to obtain, of course; and the media servers themselves to enable the

Dogfooding it, Pt 6 - Gitea

Considering the amount of configuration files necessary, this blog needs a backing source repository. And, since it's about independence of cloud services, GitHub or a third-party hosted GitLab or Gitea is out. That's exactly the sort of thing we don't want. Instead, this post

Dogfooding it, Pt 5 - PostgreSQL

Since I'll now be using configuration files rather heavily, it's probably a good idea to make those available for download. And, in the spirit of self-hosting things, why put them on GitHub when I can host Gitea and show off another service? Now, I know Gitea

Media Server, Pt 1 - Navidrome

Having set up our stack for swarm deployment, and deployed a blog server to demonstrate, I'm going to turn to deploying various media servers. The first is Navidrome, a music server. It's pretty much self-contained, so this will be quick. $ mkdir -p /srv/data/shared/media/