Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/kolonuk/get_iplayer-docker
A docker container for get-iplayer which grabs the latest release instead of bundling a static release in the container.
https://github.com/kolonuk/get_iplayer-docker
dockerfile iplayer perl
Last synced: about 2 months ago
JSON representation
A docker container for get-iplayer which grabs the latest release instead of bundling a static release in the container.
- Host: GitHub
- URL: https://github.com/kolonuk/get_iplayer-docker
- Owner: kolonuk
- Created: 2018-07-29T18:26:48.000Z (over 6 years ago)
- Default Branch: master
- Last Pushed: 2024-04-22T11:06:13.000Z (8 months ago)
- Last Synced: 2024-04-22T12:27:28.414Z (8 months ago)
- Topics: dockerfile, iplayer, perl
- Language: Shell
- Homepage:
- Size: 160 KB
- Stars: 16
- Watchers: 3
- Forks: 7
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# get_iplayer on Docker
Disappointed with the current availability of get_iplayer in docker, I created an auto-updating docker container, complete with the webgui.
For now, this uses the plain Ubuntu image, so is huge for a very simple perl program - definitely needs the packages trimming. I've added a testing branch to the github repo so that I can experiment with other base images to see if I can get this reduced in size - current uncompressed ubuntu is around 400mb. If you'd like to contribute, please fork and create a pull request, or just raise an issue on github.
## Usage
docker create \
--name get_iplayer \
-p 8181:8181 \
-v /etc/localtime:/etc/localtime:ro \
-v :/root/.get_iplayer \
-v :/root/output \
kolonuk/get_iplayer* Backup your current config and recordings.
* Mount `/root/.get_iplayer` to your config directory. This should include your `options` file and `pvr` directory. If starting from scratch, you can manually edit the `options` file created here.
* Mount `/root/output` to your recordings location.**WARNING - get_iplayer stores cookies in your browser for some default settings. Because of this, at least try to see if you can find those cookies and remove them BEFORE loading the newly installed container. For example, if you have set the recordings path in the webgui, this overrides the location in the `options` file for downloads.**
## Start
Upon first start, it will download the latest get_iplayer scripts from the official github repo .
* When starting this for the first time, it will create some nice newbie default options (enable whitespace in filenames, download subtitles, etc.).
* When starting this using existing configuration files, it will forcibly change the output location to the container's output volume location, thus hopefully, it should "just work".## Updating
There is a cron job that runs daily that checks the latest release of get_iplayer, and downloads it. It then checks to see if the pvr is running, before killing the perl process, which automatically gets restarted using the new version of the get_iplayer script. This is different from other docker containers in that the version of get_iplayer in this container is not statically included in the container, leading to a stale container.To do a manual update, you just need to re-create this container and it will have the latest version from the get_iplayer repo. I use Portainer to manage my containers, and I just need to hit the `Recreate` button.
**Watchtower will not update this container to the latest version of get_iplayer by its self. Until Docker introduces monitoring of alternative github repos for automated container builds (which trigger watchtower), this auto-update method is the best you can get.**
## Issues
* Report issues with this dockerfile
* Report issues with the get_iplayer script## About me
Just a small-time tinkerer of almost anything computer-related (servers, raspi, networks, programming, android, etc.). I am active on various places on the net, like StackExchange, github, and some mailing lists, etc., so ping me a message about anything - if I don't know, I'll know where to go to find out!## Todo
1. Check different base os's for Dockerfile
2. Remove as much gumf as possible