docker-transmission-openvpn VS tubearchivist

I think you’re in a different bubble. If no one used vpn for torrents why is one of the top docker images for transmission one to support vpns? No ones spending money on a seed box that’s just casually torrenting.

https://github.com/haugene/docker-transmission-openvpn

For torrent and open VPN this https://github.com/haugene/docker-transmission-openvpn is a great option if you can run docker.

I use haugene/transmission-openvpn to safely obtain all my Linux isos

Link to github - https://github.com/haugene/docker-transmission-openvpn

I would try the absolute path of the script and see if that does it for you. I'm running transmission on docker using haugene/docker-transmission-openvpn and that's the absolute path within the container, but YMMV if you're running the program somewhere/somehow else.

I haven’t used GlueTUN so can’t help unfortunately but I do use this one - https://github.com/haugene/docker-transmission-openvpn and it seems easier and safer (the container stops if the VPN is down)

holy hell I hadn't come across archivebox as of yet, I'll definitely be spinning this up this eve. Is the UI comfortable enough to use as a "bookmark manager"? just been setting up tubearchivist for essentially this purpose, wondering if ArchiveBox would essentially do the same

I'm using TubeArchivist to maintain this VERY large collection.

There appears to be a patch in Tubearchivest at https://github.com/tubearchivist/tubearchivist/issues/587

Personally, I use Tubearchivist.

There are others though.

https://github.com/tubearchivist/tubearchivist

I've been seeing TubeArchivist posted a lot recently.

It has been some time since the last release, but v0.4.0 is finally wrapped up. This brings a wide range of fixes and changes, particularly stability improvements, with our new file system naming convention, this should solve a bunch of previously unsolvable compatibility issues. I highly recommend reading the release notes carefully, as the filesystem migration could be a breaking change if you made changes manually there: https://github.com/tubearchivist/tubearchivist/releases/tag/v0.4.0

I saw this was a Django app so I dug around to look at their models. As far as I can tell this is all they have: https://github.com/tubearchivist/tubearchivist/blob/master/t... - just a `Account` model.

It looks like Django + SQLite is used for user accounts, but all other data storage happens in Elasticsearch.

It's an interesting design decision. I would have gone all-in on the database, and used SQLite FTS in place of Elasticsearch for simplicity, but that's my own personal favourite stack. Not saying their design is bad, just different.

Oh, so it is. I happen to run a TubeArchivist at home that grabs the videos and subtitles. Then I can search through the subtitle files for key phrases. I must have grabbed it while it was still public.

You probably want Tube Archivist. The only problem is that it’s naming convention doesn’t work with the Jellyfin YouTube Metadata Plugin.