tubearchivist VS authelia

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.

It's me and two others though I'm definitely the most active. We put a lot of effort into security best practices and one of my co-developers is currently reviewing the 4.38.0 release. It's a fairly major release with a lot of important code paths that have been improved for the future.

Our official docs can be found at https://www.authelia.com and you can find docs for a particular PR in the relevant PR. We've also linked the pre-release docs in the pre-release discussions which can be found here: https://github.com/authelia/authelia/discussions/categories/...

I use NGINX proxy with Authelia in between. Authelia blocks and blacklists faulty logins.

https://github.com/saltstack/salt https://github.com/chocolatey/choco https://github.com/nextcloud https://github.com/authelia/authelia https://github.com/grafana/grafana

If you are using HAProxy on PfSense/OPNSense, see my issue https://github.com/authelia/authelia/issues/2696

https://github.com/lldap/lldap is a very simple and lightweight LDAP solution. Works flawless with https://www.authelia.com/

Ah yeah, so I guess it's been a while since I tried and I forgot where I got stuck last time. Authelia's config.yml is absolutely massive and I'm not sure which section of their guide I should be following. In The Docker Compose section, there's "Unbundled", "Lite", and "Local". I think I want to be running the "lite" bundle, but their example compose file has a ton of Traefik stuff in it. I know I wouldn't keep the Traefik services, but do I need either secure or public?

Authelia supports SSO. If you are behind a reverse proxy it’s quite straightforward to integrate.

This should probably also be mentioned in the documentation so maybe consider mentioning this on their discussion page.