Relying on easy, simple stuff does not (always) mean a good thing let alone being good for you and your mental health. Even less so allowing proprietary, capitalism-driven developers to do whatever they want with your PC (which makes me wonder what you are even doing in this community in first place if you just "don't care"), but hey... you do you.
To use Linux properly, you've got to "unlearn" everything you know about computers and go back from the ground-up. And breaking yourself free from bad habits (that only Windows gives you) such as relying on installers to do the job for you -- i.e "double-clicking your cares away". Which can be a fun experience when compiling (The "turbo nerd way" to install things on linux) becomes "second nature", giving you the ability to taste "true freedom" of making (pretty much) anything work the way as you may seem fit.
...
No, really. You'll have a heck of a nerdgasm when you compile something that is not "normally supported" on an obscure pc/distro. You will feel like a demigod.
t. That is how I felt the first time I compiled a half-life openBSD port... on Linux. I did it "by following my gut" and everything "werked".
For the sake of "saving" your post (even as someone who has no idea how nextcloud works)... I made a quick search regarding nextcloud and the nextcloud docs says it needs a minimum of 128MiB ram per process while they recommend 512MiB which doesn't seem that much of a resource beast at all...? It COULD work, but not as good as your typical nextcloud setup with over 10 processes or something of the sort. Probably a headless/bare metal setup with dietpi, I guess?
Then again, as I said previously... this is a totally ignorant take on saving your post, but eh... who on earth would want to run nextcloud with less than 10 processes anyways? So I'm gonna go with "Yeah it does, but you'll (eventually) want to switch to a better sbc later on."
Anything beyond setting up a network-wide dns blocker on docker, so... crowdsec, fail2ban, some proxy-related stuff, zero trust tunnelers and so on.
Why? Because its overkill to my current setup and I don't see myself using em for real other than for learning purposes, and thats it.
And before someone asks "Do you protect your server at all?". Other than making some "hacky" stuff with my internet so all ports appear as closed whilst they actually aren't? Eh, not really. Still, my server is about to reach a year of running nonstop 24/7 and it has never been hacked a single time since then, so naaaw.
Mostly because the "reddit mentality" has already established in this community, where the downvote exists solely as a self-validation/"dopamine fix" feature rather than flagging a post as bad and irrelevant.
Just install it via pip and then symlink its binary file to /usr/bin.
t. Am running a live stream 24/7 on my orange pi zero 3 (via ffplay/yt-dlp) since forever.
"Why not simply add $HOME/.local/bin to $PATH?"
Because it breaks things. While symlinking it does not.
"Why?"
No idea, honestly.
Also, you can take a step further and make a tmpfs partition @ $HOME/.local and then add the following line to your .bash_profile file:
TMPDIR=$HOME/.local pip install --break-system-packages -I --no-input yt-dlp &&.
I've no idea, honestly. Does it gives me more free time to worry about more important stuff however that will (very likely) not be changed over time by money-hungry developers with false promises of unachievable anonymity and/or privacy in their applications? That I can guarantee a reasonable YES.
This is why I don't care about privacy anymore and use whatever browser works better in my pc/sbc (brave) followed by a network ad-blocker solution (nextdns).
Good ol' Windows 69. :^)