Author: Taylor Jadin

I’ve been busy with Peertube stuff lately. After getting my own instance at video.jadin.me upgraded to 5.0, I also wanted to set up object storage so I could utilize Amazon S3 or the alternatives. In this case I wanted to use Backblaze B2, as I’m already using Backblaze’s Personal backup for backing up computers in my home, and generally a fan of the simplicity of B2 compared to doing stuff in the AWS dashboard.

Here are some notes I made on how I upgraded various Peertube installs (video.jadin.me and archive.reclaim.tv, mainly) to version 5.0. Version 5 came with some big changes, and required some a new config for nginx, as well as a required setting in a new to me production.yaml file. Here are some quick notes if you are having trouble upgrading to version 5, and you are using a docker-compose based setup. There were some notes in the GitHub release for this new version that informed my notes below, but it did take me a little figuring and experimentation to make sense of all of it.

Two weeks ago, I did a stream on HTML flattening with a tool called HTTrack. I’ve been wanting to show this off for a while as I think it makes the processing of flattening a site relatively easy, plus it works across macOS, Linux, and Windows. I’ve been a little behind on blogging this one, as I didn’t have the video available on video.jadin.me until recently. This video was my test case for setting up my Peertube instance to store its videos on Backblaze B2, which is a lot like Amazon’s S3 storage, but even cheaper for many use cases.

This week I did a stream to document how I use hugo, the static site generator, for this blog that you’re reading right now!
The point of this post and stream were to show how I use this tool, but all of this is really not a good starting point if you are looking to start with hugo, or you just want to see how it works. For that, I’d recommend checking out the hugo quick start documentation!

I recently needed to back up a bunch of files, about 6GB, from a Reclaim Cloud node so here are some notes on how I was able to connect directly to the Node. I like using the Reclaim Cloud SSH Gate for SSH or SFTP access to containers most of the time, but in my case because I had so many files to sync, I wanted to use rsync, which as far as I’m aware won’t work with the SSH Gate.

In addition to the stream on a new Ghost installer, Jim and I showcased the streaming tools we used to put together the Reclaim EdTech Understanding Containers flex course as well as discussed the format of the course and future offerings for Reclaim EdTech.
And here are the chapters if you want to skip around the video:
0:00 – Intro 3:50 – OBS demo 7:09 – vdo.ninja demo 17:08 – reclaimed.

A couple of weeks ago I did a quick stream (ok it wasn’t quick, it was almost 90 minutes) on the Basics of the Command Line.
My goal was to start at the beginning, with navigating around files and folders and editing text, while picking up some tips and tricks along the way, as well show why the command line is still so useful and important. I spend a lot of time trying to drive home that you should definitely definitely use the tab key to autocomplete paths as it will make your life easier.

This is a quick little post to document something I’ve found handy! A common way to issue a Let’s Encrypt cert and get things to load on Reclaim Cloud over HTTPS is to use an NGINX Load Balancer. Here’s an example environment, one I use to run Foundry Virtual Tabletop:
The trick is some applications that you run won’t automatically redirect URLs with HTTP to HTTPS, so you have to manually type HTTPS in your address bar.

PeerTube 4.2 is out, and it has all kinds of features I’m excited about like in-place editing of videos, replays of recurring live streams (basically you can have a permanent Twitch-like URL where you can go live and then have a recording of that livestream automatically available afterward), latency settings for livestreams, and a bunch of other stuff.
I wanted to get my PeerTube instance on Reclaim Cloud upgraded, which is a docker-compose setup with the Live Chat plugin enabled, so I stopped the containers, pulled changes, and started the containers again.