And correcting it isn't an option?
GravitySpoiled
I can add as many users as I want to navidrome ?
You forgot to mention systemd
Running SELinux under a Linux distribution requires three things: An SELinux enabled kernel, SELinux Userspace tools and libraries, and SELinux Policies (mostly based on the Reference Policy). Some common Linux programs will also need to be patched/compiled with SELinux features.
Now I know why I didn't bother with selinux back when I used arch. I never had any issues with it on fedora with zero maintenance.
You have to fill out an application form to get into a private tracker. Literally just a couple of sentences about your torrent experience, why you want to join, etc. You can copy paste that paragraph and send it to 10 trackers.
What did you write that you were not accepted?
Same for nginx proxy manager. I just read upon the differences and traefik is aware of containers and shall be easier to update. I may switch to it. Thx for bringing this up.
Nginx proxy manager is super easy (for me) but traefik might be the better recommendation. Both work.
Gluetun ensures that the containers are properly connected to the vpn and that port forwarding is enabled which can be a pain in the ass.
Npm = nginxproxymanager, it forwards external requests to the right port where the containers are such that you can reach your jellyfin instance on your selfhosted/rented server
The problem you describe is that there are a hundred working ways. Each path works but you have to find it and take it.
Imo, you can reduce the list to:
how to pirate movies as a beginner
- Setup vpn
- Install qbittorrent
- Visit a tracker like 1337x.to
- Download and enjoy
How to pirate movies as a pro
- Read about torrents
- Setup vpn
- Setup docker
- Setup prowlarr
- Setup gluetun
- setup qbittorrent
- Find a tracker, any tracker, and add it to prowlarr
- Search for something on prowlarr and be happy
- Add another tracker
- Setup radarr
- Setup jellyfin
- Setup ~~nginx proxy manager~~ traefik
You have to provide info why the distro of choice is the best distro for said use case. Otherwise the reader will just pass if he doesn't like the distro. It has to be convincing
Imo, First requirement should be that it has to automatically boot, always. If a distro is not able to ensure this without major user input it's not a state of the art distro. Any system has to boot always. You shall never be left with a broken system.
I really like that you want to spend time and effort into exploring this problem formulation.
At first you need to formulate the problem and the current setting and goal.
- A user searches a distro and has a minimum requirement demand.
- What are the necessary tools a distro must have in order to fit the demand of the user?
- The goal is to find a distro that fits the demand, at least the minimum.
- Does the user start with a computer or will he buy a new one?
- what are all requirements?
- which distro fits those requirements, which doesn't, and why? Is it a out of the box problem or is just a package missing?
it's very difficult
Why am I the author?
What software is literally made for this?