

Is 172.17.0.1 like dockers loopback for its own services?
Is 172.17.0.1 like dockers loopback for its own services?
I had considered the VPN route, but i think its enough of a technical hurdle for other people that it would stop my parents and friends from being able/willing to get onto the audiobookshelf server
I had considered not using nginx for precisely those reasons, but like the plex server i want to make it available to my family and friends and so the nginx reverse proxy build seemed to be the most widely applicable and still secure option so I only need to tell them to download audiobookshelf and point it at the correct domain name.
Thank you so much this is very helpful, I’ll definitely be taking a run at it with all of this advice in mind this week. When you mention running the whole thing as a single stack does that mean getting all of it running inside a single docker container such that it only takes the 1 docker run command? Is it a requirement to get them able to talk or just a more elegant way to have the entirety of the server running in a singular container instead of spread across several?
I know, and that’s on my to-do list, but I wanted to get this up and running at least once before upgrading and potentially having to start from square 1.
Ive got a reverse proxy config that was available in the Audiobookshelf github documentation, I was mainly struggling to understand how to get all of the parts working together. Thanks for the help