Your self hosted YouTube media server
Table of contents:
- Wiki with FAQ
- Core functionality
- Problem Tube Archivist tries to solve
- Extended Universe
- Installing and updating
- Getting Started
- Common Errors
- Known limitations
- Subscribe to your favorite YouTube channels
- Download Videos using yt-dlp
- Index and make videos searchable
- Play videos
- Keep track of viewed and unviewed videos
Tube Archivist on YouTube
Problem Tube Archivist tries to solve
Once your YouTube video collection grows, it becomes hard to search and find a specific video. That's where Tube Archivist comes in: By indexing your video collection with metadata from YouTube, you can organize, search and enjoy your archived YouTube videos without hassle offline through a convenient web interface.
- Browser Extension Tube Archivist Companion, for Firefox and Chrome
- Tube Archivist Metrics to create statistics in Prometheus/OpenMetrics format.
Installing and updating
There's dedicated user-contributed install steps under docs/Installation.md for podman, Unraid, Truenas and Synology which you can use instead of this section if you happen to be using one of those. Otherwise, continue on.
For minimal system requirements, the Tube Archivist stack needs around 2GB of available memory for a small testing setup and around 4GB of available memory for a mid to large sized installation.
Note for arm64 hosts: The Tube Archivist container is multi arch, so is Elasticsearch. RedisJSON doesn't offer arm builds, but you can use the image
bbilly1/rejson, an unofficial rebuild for arm64.
This project requires docker. Ensure it is installed and running on your system.
Save the docker-compose.yml file from this reposity somewhere permanent on your system, keeping it named
docker-compose.yml. You'll need to refer to it whenever starting this application.
Edit the following values from that file:
HOST_UID: your UID, if you want TubeArchivist to create files with your UID. Remove if you are OK with files being owned by the the container user.
HOST_GID: as above but GID.
TA_HOST: change it to the address of the machine you're running this on. This can be an IP address or a domain name.
TA_PASSWORD: pick a password to use when logging in.
ELASTIC_PASSWORD: pick a password for the elastic service. You won't need to type this yourself.
TZ: your time zone. If you don't know yours, you can look it up here.
verysecretto match the ELASTIC_PASSWORD you picked above.
By default Docker will store all data, including downloaded data, in its own data-root directory (which you can find by running
docker info and looking for the "Docker Root Dir"). If you want to use other locations, you can replace the
es: volume names with absolute paths; if you do, remove them from the
volumes: list at the bottom of the file.
From a terminal,
cd into the directory you saved the
docker-compose.yml file in and run
docker compose up --detach. The first time you do this it will download the appropriate images, which can take a minute.
You can follow the logs with
docker compose logs -f. Once it's ready it will print something like
celery@1234567890ab ready. At this point you should be able to go to
http://your-host:8000 and log in with the
You can bring the application down by running
docker compose down in the same directory.
Use the latest (the default) or a named semantic version tag for the docker images. The unstable tag is for intermediate testing and as the name implies, is unstable and not be used on your main installation but in a testing environment.
Tube Archivist depends on three main components split up into separate docker containers:
The main Python application that displays and serves your video collection, built with Django.
- Serves the interface on port
- Needs a volume for the video archive at /youtube
- And another volume to save application data at /cache.
- The environment variables
REDIS_HOSTare needed to tell Tube Archivist where Elasticsearch and Redis respectively are located.
- The environment variables
HOST_GIDallows Tube Archivist to
chownthe video files to the main host system user instead of the container user. Those two variables are optional, not setting them will disable that functionality. That might be needed if the underlying filesystem doesn't support
- Set the environment variable
TA_HOSTto match with the system running Tube Archivist. This can be a domain like example.com, a subdomain like ta.example.com or an IP address like 192.168.1.20, add without the protocol and without the port. You can add multiple hostnames separated with a space. Any wrong configurations here will result in a
Bad Request (400)response.
- Change the environment variables
TA_PASSWORDto create the initial credentials.
ELASTIC_PASSWORDis for the password for Elasticsearch. The environment variable
ELASTIC_USERis optional, should you want to change the username from the default elastic.
- For the scheduler to know what time it is, set your timezone with the
TZenvironment variable, defaults to UTC.
If you have a collision on port
8000, best solution is to use dockers HOST_PORT and CONTAINER_PORT distinction: To for example change the interface to port 9000 use
9000:8000 in your docker-compose file.
Should that not be an option, the Tube Archivist container takes these two additional environment variables:
- TA_PORT: To actually change the port where nginx listens, make sure to also change the ports value in your docker-compose file.
- TA_UWSGI_PORT: To change the default uwsgi port 8080 used for container internal networking between uwsgi serving the django application and nginx.
Changing any of these two environment variables will change the files nginx.conf and uwsgi.ini at startup using
sed in your container.
You can configure LDAP with the following environment variables:
true) Set to anything besides empty string to use LDAP authentication instead of local user authentication.
ldap://ldap-server:389) Set to the uri of your LDAP server.
true) Set to anything besides empty string to disable certificate checking when connecting over LDAPS.
uid=search-user,ou=users,dc=your-server) DN of the user that is able to perform searches on your LDAP account.
yoursecretpassword) Password for the search user.
uid) Bind attribute used to map LDAP user's username
givenName) Bind attribute used to match LDAP user's First Name/Personal Name.
sn) Bind attribute used to match LDAP user's Last Name/Surname.
ou=users,dc=your-server) Search base for user filter.
(objectClass=user)) Filter for valid users. Login usernames are matched using the attribute specified in
TA_LDAP_USER_ATTR_MAP_USERNAMEand should not be specified in this filter.
When LDAP authentication is enabled, django passwords (e.g. the password defined in TA_PASSWORD), will not allow you to login, only the LDAP server is used.
Note: Tube Archivist depends on Elasticsearch 8.
bbilly1/tubearchivist-es to automatically get the recommended version, or use the official image with the version tag in the docker-compose file.
Stores video meta data and makes everything searchable. Also keeps track of the download queue.
- Needs to be accessible over the default port
- Needs a volume at /usr/share/elasticsearch/data to store data
Follow the documentation for additional installation details.
Functions as a cache and temporary link between the application and the file system. Used to store and display messages and configuration variables.
- Needs to be accessible over the default port
- Needs a volume at /data to make your configuration changes permanent.
Redis on a custom port
For some architectures it might be required to run Redis JSON on a nonstandard port. To for example change the Redis port to 6380, set the following values:
- Set the environment variable
REDIS_PORT=6380to the tubearchivist service.
- For the archivist-redis service, change the ports to
- Additionally set the following value to the archivist-redis service:
command: --port 6380 --loadmodule /usr/lib/redis/modules/rejson.so
Updating Tube Archivist
You will see the current version number of Tube Archivist in the footer of the interface so you can compare it with the latest release to make sure you are running the latest and greatest.
- There can be breaking changes between updates, particularly as the application grows, new environment variables or settings might be required for you to set in the your docker-compose file. Always check the release notes: Any breaking changes will be marked there.
- All testing and development is done with the Elasticsearch version number as mentioned in the provided docker-compose.yml file. This will be updated when a new release of Elasticsearch is available. Running an older version of Elasticsearch is most likely not going to result in any issues, but it's still recommended to run the same version as mentioned. Use
bbilly1/tubearchivist-esto automatically get the recommended version.
There is a Helm Chart available at https://github.com/insuusvenerati/helm-charts. Mostly self-explanatory but feel free to ask questions in the discord / subreddit.
Elastic Search in Docker requires the kernel setting of the host machine
vm.max_map_count to be set to at least 262144.
To temporary set the value run:
sudo sysctl -w vm.max_map_count=262144
To apply the change permanently depends on your host operating system:
- For example on Ubuntu Server add
vm.max_map_count = 262144to the file /etc/sysctl.conf.
- On Arch based systems create a file /etc/sysctl.d/max_map_count.conf with the content
vm.max_map_count = 262144.
- On any other platform look up in the documentation on how to pass kernel parameters.
Permissions for elasticsearch
If you see a message similar to
failed to obtain node locks, tried [/usr/share/elasticsearch/data] and
maybe these locations are not writable when initially starting elasticsearch, that probably means the container is not allowed to write files to the volume.
To fix that issue, shutdown the container and on your host machine run:
chown 1000:0 -R /path/to/mount/point
This will match the permissions with the UID and GID of elasticsearch process within the container and should fix the issue.
The Elasticsearch index will turn to read only if the disk usage of the container goes above 95% until the usage drops below 90% again, you will see error messages like
disk usage exceeded flood-stage watermark, link.
Similar to that, TubeArchivist will become all sorts of messed up when running out of disk space. There are some error messages in the logs when that happens, but it's best to make sure to have enough disk space before starting to download.
- Go through the settings page and look at the available options. Particularly set Download Format to your desired video quality before downloading. Tube Archivist downloads the best available quality by default. To support iOS or MacOS and some other browsers a compatible format must be specified. For example:
- Subscribe to some of your favorite YouTube channels on the channels page.
- On the downloads page, click on Rescan subscriptions to add videos from the subscribed channels to your Download queue or click on Add to download queue to manually add Video IDs, links, channels or playlists.
- Click on Start download and let Tube Archivist to it's thing.
- Enjoy your archived collection!
We have come far, nonetheless we are not short of ideas on how to improve and extend this project. Issues waiting for you to be tackled in no particular order:
- User roles
- Podcast mode to serve channel as mp3
- Implement PyFilesystem for flexible video storage
- Implement Apprise for notifications (#97)
- User created playlists, random and repeat controls (#108, #220)
- Auto play or play next link (#226)
- Multi language support
- Show total video downloaded vs total videos available in channel
- Add statistics of index
- Download speed schedule (#198)
- Auto ignore videos by keyword (#163)
- Custom searchable notes to videos, channels, playlists (#144)
- Download video comments [2022-11-30]
- Show similar videos on video page [2022-11-30]
- Implement complete offline media file import from json file [2022-08-20]
- Filter and query in search form, search by url query [2022-07-23]
- Make items in grid row configurable to use more of the screen [2022-06-04]
- Add passing browser cookies to yt-dlp [2022-05-08]
- Add SponsorBlock integration [2022-04-16]
- Implement per channel settings [2022-03-26]
- Subtitle download & indexing [2022-02-13]
- Fancy advanced unified search interface [2022-01-08]
- Auto rescan and auto download on a schedule [2021-12-17]
- Optional automatic deletion of watched items after a specified time [2021-12-17]
- Create playlists [2021-11-27]
- Access control [2021-11-01]
- Delete videos and channel [2021-10-16]
- Add thumbnail embed option [2021-10-16]
- Create a github wiki for user documentation [2021-10-03]
- Grid and list view for both channel and video list pages [2021-10-03]
- Un-ignore videos [2021-10-03]
- Dynamic download queue [2021-09-26]
- Backup and restore [2021-09-22]
- Scan your file system to index already downloaded videos [2021-09-14]
- Video files created by Tube Archivist need to be playable in your browser of choice. Not every codec is compatible with every browser and might require some testing with format selection.
- Every limitation of yt-dlp will also be present in Tube Archivist. If yt-dlp can't download or extract a video for any reason, Tube Archivist won't be able to either.
- There is currently no flexibility in naming of the media files.
The best donation to Tube Archivist is your time, take a look at the contribution page to get started.
Second best way to support the development is to provide for caffeinated beverages:
- GitHub Sponsor become a sponsor here on GitHub
- Paypal.me for a one time coffee
- Paypal Subscription for a monthly coffee
- ko-fi.com for an alternative platform
Big thank you to Digitalocean for generously donating credit for the tubearchivist.com VPS and buildserver.