Homelab Adventures (Page 2)

Homelab Adventures

Sign in Subscribe

More issues

Media Server, Pt 4 - Sabnzbd

Now we're starting the fun. Note that the current configuration of the main branch does not include outbound connectivity for the media server, nor will it. This is to make it a conscious choice on the part of my readers to permit, or not permit, their containers to

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/

Improving the Process

At this point, we have a small handful of containers running, and are likely looking at adding more to the list. It's only reasonable to consider the maintainability of the resulting system, and the fact of the matter is, the prospects of keeping going with individual containers on

Dogfooding it, Pt 4 - Traefik

Traefik is a reverse proxy with container integration. With properly set up containers and networking, it's minimal configuration to get it working in this lab - much easier than nGinx. Our directory structure for this consists of a handful of directories. We do need the Traefik UID to

Dogfooding it, Pt 3 - Ghost

At this point, we have a Docker server and a PerconaDB / MySQL container. It's time to install the Ghost CMS itself. First, we'll need to establish the database user for it. Ghost itself does not support a shared secret, so we're just going to