To watch stuff without ads and tracking, but still streaming, you can use clipious or newpipe on Android and android tv. If you want to replace the entire YouTube GUI with an ad free selfhosted one, check out

https://github.com/iv-org/invidious

Nextcloud works great for document management, if you additionally install tesseract OCR and Elasticsearch. Then you can use any smartphone document-scanner (I personally use "swift scan") to add new documents via WebDAV Upload, but I think most of them support WebDAV nowadays. The Nextcloud app even has a document scanner feature built in, but it's not very good.

I have been reading about the features of paperless-ng and I don't see what that software additionally brings to the table that a properly setup nextcloud cannot do. Only that I have Nextcloud anyways and it can do much more than document management and I love to have all aspects of my "personal cloud" in one software tool.

I don't know how much configurable invidious is in terms of allow-listing content, but unless you want to locally cache the content you want them to see - which seems a lot of work, I guess that's the way to go

https://github.com/iv-org/invidious

The question is not so much if you have enough physical ram but if your docker management tool has established resource limits for the containers. Oom killer will stop the process regardless of the fact that there is enough free memory if the container goes over its Ressource contraints.

https://stackoverflow.com/questions/42345235/how-to-specify-memory-cpu-limit-in-docker-compose-version-3

There is the middle ground of retrieving your mail from a mail Provider and serving it from a self hosted IMAP. That way you don't handle in- outgoing smtp but handle it locally.

So, open a terminal and check if the device is there on your system?

I dont think this makes any sense at all. There is no fixed resource requirements in any of your VM's ... ALL of them can make use of having more resources when they need it. Thats why probably the Proxmox (or Linux Kernel Developers, or Android developers) spend a LOT OF TIME thinking about governing resources. It makes no sense that an idling OS is sitting on a reservee core when your 25 Containers would need to do stuff in parallel.

I think you should resource the overall concept of your setup.

Usually "a server" runs a lot of different things and programs. Multicore is especially beneficial in that scenario because even if a certain program does not support multicore processing, the os will just run "the other app" on another core.

So the concept of which app can use multicore processing is mainly relevant for desktop PC's that run "one big app".

So why put the UI on the server and not in the client??

https://github.com/jely2002/youtube-dl-gui

Can you not just send the users request to two different URL, based on the decision if it needs auth or not? That would not be authelias task but your internal url routers. Authelia would handle the authentication on the path that requires auth and your proxy would directly serve the "open" content. The logic would have to take place in your app.

myapp.org/ checks what it's going to be

myapp.org/secret/ serves content you need to be authenticated for

myapp.ort/open/ serves content that doesn't need auth.

When I was working in companies with very restrictive firewalls and needed to access my homeserver via SSH, I was using TOR browser (which exists as portable versions so you need to install anything which you are not allowed to). TOR Browser creates a socks proxy, which you can then use from kitty/putty ssh (which also have portable versions) to dial out.

Depends on the vulnerability