self-hosted_docker_setups VS tubearchivist

Credits to r/selfhosted, pi-hosted, self-hosted_docker_setups

This might be of help to you

This repo has a lot of pre-made docker compose files. I'd recommend starting with AdGuard-Home, Homer, Watchtower, and Code-Server (if you code).

I consolidated all the docker-compose + any additional configuration files for these apps on GitHub to serve as reference. Here's the link to the repo - https://github.com/abhilesh/self-hosted_docker_setups

Here's the docker-compose - https://github.com/abhilesh/self-hosted_docker_setups/tree/main/vikunja

Here's mine to serve as an example - https://github.com/abhilesh/self-hosted_docker_setups/tree/main/wallabag

Here's the config file for Homer, I use a yaml file but it can be easily converted to json - https://github.com/abhilesh/self-hosted_docker_setups/blob/main/homer/config.yml

I am consolidating the docker-compose files for my setup here - https://github.com/abhilesh/self-hosted_docker_setups

I use SurfShark's VPN services so here's my docker-compose file with the entire *Arr stack and two torrent clients connected through the VPN - https://github.com/abhilesh/self-hosted_docker_setups/tree/main/surfshark

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

Personally, I use Tubearchivist.

There are others though.

https://github.com/tubearchivist/tubearchivist

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.

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

Yeah, I've been thinking more and more lately that I really ought to setup Tube Archivist and backup all my favourite channels' videos in case of the worst, but I just don't have room on my server right now for all that video

tube archivist

Perhaps this does what you are looking for? I didn't dive too deeply into limitations. https://www.tubearchivist.com/