lxd-dashboard VS tubearchivist

LXD Dashboard for easy managing lxc https://lxdware.com

The Ararat project lacks screenshots or any detail, so I can't quite say what direction it's heading as compared to the other several LXD-specific dashboards/control panels out there (lxdware, LxdMosaic and others).

https://lxdware.com/ https://github.com/lxdware/lxd-dashboard or the older https://github.com/AdaptiveScale/lxdui.

In that case, let's throw caution to the wind! Ubuntu (debian-based) + lxd (manages lxc containers and qemu VM) + an lxd webUI (https://github.com/turtle0x1/LxdMosaic or https://github.com/lxdware/lxd-dashboard). Unconventional option as lxd usually flies under the radar, but it is a nice alternative to proxmox.

+1, but there are two community webUIs for LXD: https://github.com/lxdware/lxd-dashboard and https://github.com/turtle0x1/LxdMosaic

You won't have a single webUI to manage everything. But LXD has a couple different webUIs to manage those containers and VMs: https://lxdware.com/ and https://github.com/turtle0x1/LxdMosaic

Here two examples. I personally used the first one in the past and it was great. (now I just don't have lxc containers anymore). https://lxdware.com/ https://github.com/turtle0x1/LxdMosaic

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.