It would take me hours to figure out how to do all that with Apache.
This is an obvious exaggeration. It would longer just to consolidate media into Plex libraries.
> It would take me hours to figure out how to do all that with Apache.
Wow. Here's a clue
sudo cp /etc/apache2/httpd.conf /etc/apache2/https.conf.bak
sudo vi /etc/apache2/httpd.conf
# hint: learn apache once, use many times
sudo ln -s /Directories/you/want/apache/to/see /Library/WebServer/Documents/
sudo apachectl start
Took me less than 10 minutes.Thanks for the script. I have no interest in learning how it works, though, I just want to watch a darn movie…
Unnecessary step, and if it only takes you 10 seconds, you really have no media to speak of: when it is TB of media, you're fucked.
> Thanks for the script.
Not a script, just a few loose commands.
We could endlessly debate which cognitive model is best but you know, that’s stupid… because there is only one…
…Packaged executables should die off. I want to compose electron state in a machine not some randos config formats and syntax art.
I don’t understand Apache OR Plex (or nginx or Docker, etc). Would prefer logic simply be modeled in open code libs I can list in a dep file and run; but software _products_ whether open like Apache or closed like Plex, with a bunch of opinions on acceptable UX/CX are foisted on me by Apache or Plex devs.
I’m just as sick of learning one asinine tribal jargon after as I am the arguments about which tribal jargon is superior!
Bring on the AI chips that abstract away software. Bleh what a trashy gossip fueled industry.
That's a wrong assumption. For many (most?) users of Plex, that's pretty much the entire point. :)
Try it out yourself, and then see what you reckon it would take to set up Apache to match Plex's functionality. It'll take significant effort, if it's even capable.