Project One-Click: All-in-One Installations of Docker Extensions and CDVR Custom Channels

[chDVRuser]

VERY NICE!

I tested some combinations and they work fine on my Synology NAS.

And this may be some good news for Windows users, being able to use host mode network to run Channels DVR Server containers.

Project One-Click: All-in-One Installations of Docker Extensions and CDVR Custom Channels

Good news it looks like windows users might not be locked out from 4.34 Docker release notes: Host networking is supported on Docker Desktop version 4.34 and later. To enable this feature: Sign in to your Docker account in Docker Desktop. Navigate to Settings. Under the Resources tab, select Network. Check the Enable host networking option. Select Apply and restart. This feature works in both directions. This means you can access a server that is running in a container from your host and you c…

And looking at their release notes, it appears this is available on Windows, Mac and Linux

Release notes

[Jay1987]

OK. This has me feeling like a IDIOT! I have no clue what to do. I am am trying linux again (Last time I used linux on regular would of been 2005ish).

1. I installed ubuntu
2. I Installed docker
3. I installed Olive Tin via *.deb package
4. Olive tin shows up in webbrowser. Does not show up in portainer (Probably because I installed by package)
5. Created a token and copied. Now that do I do with it.
6. WTF do I do now to setup project 1 click. There is a envirorment variable you list. Where am I supposed to create that file. I am frustrated. I am sure its completely obvious and I am just missing it. But what do I do next

ive somewhat scrolled the 200 comments. I searched comments for installation. I am not seeing it.

[bnhf]

@Jay1987

I installed Olive Tin via *.deb package

OliveTin-for-Channels is a very specialized version of the generic OliveTin project (which is what you installed).

Your steps 1 and 2 are correct, but you went off the tracks after that. The OliveTin-for-Channels Docker Compose, and sample environment variables are in a number of places on the forum, including Post #1 in this thread.

Maybe this video from earlier in the thread would be useful as well.

[Jay1987]

Oh. . . Yup. I didnt relize different versions of olivetin. I think i got frustrated after that, frustrated Jake is not rational jake.

[bnhf]

@Jay1987

I didnt relize different versions of olivetin.

You'll probably want to uninstall the generic deb package version -- so it doesn't conflict...

[Edwin_Perez]

I noticed when I create a Pluto using one Click it added to the server.... this is great. I see it does it for all.

[mjitkop]

Exactly right, @Edwin_Perez.

The idea with Project One-Click was that once you click the button:

1. Set up Docker (via Portainer stack)
2. Create the source on the server

All done automagically.

The user doesn't need to mess around with settings.

[catdroid]

Thank you @bnhf, @mjitkop, and anyone else who has contributed to this excellent project.

A quick feature request: Adding in a Threadfin container deployment.

GitHub - Threadfin/Threadfin: an M3U proxy for Kernel/Plex/Jellyfin/Emby...

Thanks for your consideration!

[Edwin_Perez]

You do not need threadfin to use Channels DVR in Plex... and you can add more than 480 Channels.

HACK: Use Channels DVR as a Plex tuner - Playground / Hacks - Channels Community

[catdroid]

Yes, I know. The new functionality works exactly as intended and that's great.

However, Threadfin has other abilities (channel mapping, channel backups, etc.) beyond the ability to present the IP stream to Plex, and that is why I'm asking.

[KineticMan]

I use Threadfin as a "pre-filter" for a custom channel source to grab Categories from my provider before presenting to Channels (similiar to a m3u4u i suppose-just self hosted). Very helpful as my provider likes to change the channel-id and breaks my Gracenote integration. since i pre-filter in Threadfin, i can avoid this

[bnhf]

@catdroid

Adding in a Threadfin container deployment.

I'll take a look. Thanks for the suggestion.

[bnhf]

@catdroid

A quick feature request: Adding in a Threadfin container deployment.

I'm looking at something like this for a Docker Compose and environment variables. Anything else I should add?:

version: '3.9'
services:
  threadfin:
    image: fyb3roptik/threadfin:${TAG}
    container_name: threadfin
    ports:
      - ${HOST_PORT}:34400
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=${TZ}
    volumes:
      - ${HOST_DIR}/conf:/home/threadfin/conf
      - ${HOST_DIR}/temp:/tmp/threadfin:rw
    restart: unless-stopped

With these example env vars:

TAG=latest
HOST_PORT=34400
PUID=1001
PGID=1001
TZ=America/Los_Angeles
HOST_DIR=/data/threadfin

[catdroid]

That looks good to me.

[ItsMeMica]

Hello,
My apologies in advance for the question. I've been trying to get the Olive Tin/One-Click setup working. I was following a YouTube video found here along with instructions but can't find it now. I got as far as installing Portainer. Is there a single set of instructions written or video for getting this setup and working ??.

Thank you......

[chDVRuser]

This video?

@bnhf

And, here's step-by-step video I put together on installing OliveTin-for-Channels:

OliveTin for Channels Installation

[bnhf]

@catdroid

A quick feature request: Adding in a Threadfin container deployment.

Apologies for the delay. Threadfin has now been added to Project One-Click:

[Matthew_Thompson]

What if your Portainer port is not 9443? How do you alter that in the stack? Container?

[bnhf]

@Matthew_Thompson

What if your Portainer port is not 9443?

I believe my thinking at the time must have been "Anyone that wants to use an alternate port for Portainer can go pound sand". Kidding aside -- apologies for that -- I'll add an environment variable to handle an alternative to 9443.

[bnhf]

@Matthew_Thompson

How do you alter that in the stack?

I've added an environment variable to support a custom https port for Portainer. This requires the version of OliveTin published today, along with this latest Docker Compose:

version: '3.9'
services:
  olivetin: # This docker-compose requires little or no editing. Set the Environment variables section of Portainer.
    # 2025.01.22
    # GitHub home for this project: https://github.com/bnhf/OliveTin.
    # Docker container home for this project with setup instructions: https://hub.docker.com/repository/docker/bnhf/olivetin.
    image: bnhf/olivetin:${TAG} # Add the tag like latest or test to the environment variables below.
    container_name: olivetin
    hostname: olivetin
    dns_search: ${DOMAIN} # For Tailscale users using Magic DNS, add your Tailnet (tailxxxxx.ts.net) to use hostnames for remote nodes, otherwise use your local domain name.
    ports:
      - ${HOST_PORT}:1337
    environment:
      - CHANNELS_DVR=${CHANNELS_DVR_HOST}:${CHANNELS_DVR_PORT} # Add your Channels DVR server in the form CHANNELS_DVR_HOST=<hostname or ip> and CHANNELS_DVR_PORT=<port>.
      #- CHANNELS_DVR_ALTERNATES=${CHANNELS_DVR2_HOST}:${CHANNELS_DVR2_PORT} # Space separated list of alternate Channels DVR servers to choose from in the form hostname:port or ip:port.
      - CHANNELS_CLIENTS=${CHANNELS_CLIENTS} # Space separated list of Channels DVR clients you'd like notifications sent to in the form hostname or IP.
      - ALERT_SMTP_SERVER=${ALERT_SMTP_SERVER} # SMTP server to use for sending alert e-mails. smtp.gmail.com:587 for example.
      - ALERT_EMAIL_FROM=${ALERT_EMAIL_FROM} # Sender address for alert e-mails.
      - ALERT_EMAIL_PASS=${ALERT_EMAIL_PASS} # SMTP "app" password established through GMail or Yahoo Mail. Do not use your everyday e-mail address.
      - ALERT_EMAIL_TO=${ALERT_EMAIL_TO} # Recipient address for alert e-mails.
      - UPDATE_YAMLS=${UPDATE_YAMLS} # Set this to true to update config.yaml.
      - UPDATE_SCRIPTS=${UPDATE_SCRIPTS} # Set this to true to update all included scripts.
      - TZ=${TZ} # Add your local timezone in standard linux format. E.G. US/Eastern, US/Central, US/Mountain, US/Pacific, etc.
      - PORTAINER_TOKEN=${PORTAINER_TOKEN} # Generate via <username> dropdown (upper right of WebUI), "My account", API tokens.
      - PORTAINER_HOST=${PORTAINER_HOST} # Hostname or IP of the Docker host you're running Portainer on.
      - PORTAINER_PORT=${PORTAINER_PORT} # https port you're running Portainer on. 9443 is the default.
    volumes:
      - ${HOST_DIR}/olivetin:/config # Add the parent directory on your Docker you'd like to use.
      - ${DVR_SHARE}:/mnt/${CHANNELS_DVR_HOST}-${CHANNELS_DVR_PORT} # This can either be a Docker volume or a host directory that's connected via Samba or NFS to your Channels DVR network share.
      - ${LOGS_SHARE}:/mnt/${CHANNELS_DVR_HOST}-${CHANNELS_DVR_PORT}_logs # This can either be a Docker volume or a host directory that's connected via Samba or NFS to your Channels DVR logs network share.
      - ${TUBEARCHIVIST_SHARE}:/mnt/${CHANNELS_DVR_HOST}-${CHANNELS_DVR_PORT}_ta # This can either be a Docker volume or a host directory that's connected via Samba or NFS to your TubeArchivist videos network share.
      #- ${DVR2_SHARE}:/mnt/${CHANNELS_DVR2_HOST}-${CHANNELS_DVR2_PORT} # Note that these volume mounts should always be to /mnt/hostname-port or /mnt/ip-port (dash rather than a colon between).
      #- ${LOGS2_SHARE}:/mnt/${CHANNELS_DVR2_HOST}-${CHANNELS_DVR2_PORT}_logs # This can either be a Docker volume or a host directory that's connected via Samba or NFS to your Channels DVR logs network share.
      #- ${TUBEARCHIVIST2_SHARE}:/mnt/${CHANNELS_DVR2_HOST}-${CHANNELS_DVR2_PORT}_ta # This can either be a Docker volume or a host directory that's connected via Samba or NFS to your TubeArchivist videos network share.
      - /var/run/docker.sock:/var/run/docker.sock
    restart: unless-stopped

  static-file-server:
    image: halverneus/static-file-server:latest
    container_name: static-file-server
    dns_search: ${DOMAIN}
    ports:
      - ${HOST_SFS_PORT}:8080
    environment:
      - FOLDER=${FOLDER}
    volumes:
      - ${HOST_DIR}/olivetin/data:${FOLDER}
    restart: unless-stopped

#volumes: # use this section if you've setup a docker volume named channels-dvr, with CIFS or NFS, to bind to /mnt/dvr inside the container. Set ${HOST_DIR} to channels-dvr (HOST_DIR=channels_dvr) in that example.
  #channels-dvr:
    #external: true
  #channels-dvr-logs:
    #external: true
  #tubearchivist:
    #external: true

And here's a set of example env vars:

TAG=latest
DOMAIN=tailxxxxx.ts.net
HOST_PORT=1337
CHANNELS_DVR_HOST=local-server
CHANNELS_DVR_PORT=8089
CHANNELS_DVR2_HOST=another-server
CHANNELS_DVR2_PORT=8089
CHANNELS_CLIENTS=appletv4k-den firestick-bedroom
ALERT_SMTP_SERVER=smtp.gmail.com:587
ALERT_EMAIL_FROM=username@gmail.com
ALERT_EMAIL_PASS=xxxxxxxxxxxxxxxx
ALERT_EMAIL_TO=username@gmail.com
UPDATE_YAMLS=true
UPDATE_SCRIPTS=true
TZ=US/Mountain
HOST_DIR=/data
DVR_SHARE=/mnt/dvr
LOGS_SHARE=/mnt/channelsdvr
TUBEARCHIVIST_SHARE=/mnt/dvr
HOST_SFS_PORT=8080
FOLDER=/web
PORTAINER_TOKEN=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
PORTAINER_HOST=docker-host
PORTAINER_PORT=9443

If you could confirm back here once you've tested it with your setup, I'll update the compose in the various locations it can be found on this forum and on Docker Hub.