Running Usenet Stack as Docker Containers

In Running Usenet Stack on Kubernetes, I covered how to deploy a Usenet stack onto Kubernetes.

Image result for docker container

As it turned out, Kubernetes has won the race as the orchestrator of choice but not everyone is running it in their home lab just yet. I received multiple requests how to translate my YAML files into Docker run commands.

This image has an empty alt attribute; its file name is text256.png

sudo docker run -d –name=radarr -e PUID=1000 -e PGID=1000 -e TZ=America/New_York -p 7878:7878 -v change_me:/config -v change_me:/movies -v change_me:/downloads –restart unless-stopped linuxserver/radarr

The above command will launch a docker container from the linuxserver/radarr image and publish the application on port 7878.
Before you just run the above command, please make sure to change following paths:

/config
stores the configuration files

/movies
location of the downloaded movies after it has been moved from the /downloads folder

/downloads
download folder where your NZBGet or SABnzbd app will store the downloads

sudo docker run -d –name=sonarr -e PUID=1000 -e PGID=1000 -e TZ=America/New_York -p 8989:8989 -v change_me:/config -v change_me:/tv -v change_me:/downloads –restart unless-stopped linuxserver/sonarr

This is basically doing the same as the container for Radarr, except this application will be launched on port 8989. As with Radarr, Sonarr all needs some paths updated before launching the above command:

/config
stores the configuration files

/tv
location of the downloaded tv shows after they have been moved from the /downloads folder

/downloads
download folder where your NZBGet or SABnzbd app will store the downloads

Image result for nzbget

sudo docker run -d –name=nzbget -e PUID=1000 -e PGID=1000 -e TZ=America/New_York -p 6789:6789 -v change_me:/config -v change_me:/downloads –restart unless-stopped linuxserver/nzbget

In my other post, I covered SABnzbd but I’ve recently chosen to go with NZBGet on Docker as it has been more reliant in my lab. NZBGet’s default port is 6789 and if you don’t have a good reason, I would just keep it on the default port. NZBGet has one configuration less than Sonarr and Radarr:

/config
stores the configuration files

/downloads
download folder where your NZBGet is going to store all downloads. This folder needs to be accessible by Sonarr and Radarr.

Create Rubrik SLAs from a CSV File

If you own a Brik, you are familiar with creating new SLAs as it is one of the first things you would do after getting a Brik deployed.

In the world of Rubrik, everything is build around Service Level Agreements. With Rubrik’s unique approach to use SLAs for Backup and Recovery tasks, we have dramatically simplified the Backup Admin’s daily work. Traditionally a Backup Admin would create multiple backup jobs for full, incremental, hourly, daily, weekly, monthly and yearly backups. Additionally the backup admin would create some archival and replication jobs. With Rubrik’s SLA approach all of this can done within a single SLA and dramatically simplify the operational overhead associated with backup jobs.

Sometimes, a single or even a handful of SLAs might not be enough. In this case using the Rubrik interface becomes time-consuming. Luckily Rubrik has an API-First Architecture which means everything you can do in the GUI, can also be done via the APIs.

To make Rubrik’s API even easier to digest, we have a build-in API Explorer. You can get access to it via https:///docs/v1/playground

Read More

Running Usenet Stack on Kubernetes

Some of the most common applications in a Usenet Stack are SABnzbd, Sonarr and Radarr. SABnzbd is a binary newsreader which handles download from Usenet. Sonarr acts a PVR for TV shows and Radarr is a fork of Sonarr is a PVR for Movies. This post will show to deploy a Usenet Stack on Kubernetes

I recently helped out a friend to get these apps deployed on Kubernetes and I published the YAML files. You can find the files on my Github repo but I will share them further down as well.

 

Read More

Kubernetes with Mixed CPU Architecture

Creating a Raspberry Pi Kubernetes cluster is straight forward, however it becomes more complicated when you want to mix and match kubernetes nodes of different CPU architectures.

I recently deployed a new Kubernetes cluster in my home lab which initially consisted of two Ubuntu nodes running kubeadm and are  VMs on VMware ESXi. Last night I tried to add a Raspberry Pi  and ran into a couple of issues which I resolved and describe further down to save you some time.

Read More

Pipedrive and Zendesk Integration

If your Customer Service System and your Sales CRM are separated it is important to integrate the systems. Without a proper integration either your Sales or Customer Service team might be missing important informations. This free Pipedrive and Zendesk integration will help you solve this issue.

Recently I had to use Zendesk as our customer success system and Pipedrive as our Sales CRM. I have worked with Salesforce for the past 6-8 years and love it. Moving to Zendesk and Pipedrive was quiet a bit of change for me. While these two systems are cheaper than Salesforce they do have a couple of drawbacks. When I started out with both systems I was looking for a Pipedrive and Zendesk integration and came across the official Pipedrive plugin for Zendesk. Read More