NUsability question: we have a guide for jellyfin, is it hard to find?
NAh, okay
N(I'm glad you found the config!)
NReally? What would make it easier to find?
NWe recently reworked the readme to make it shorter, including links to a separate "integration guide" page
NAny suggestions on improving it is welcome
NMaybe the config can use some work, but I'm surprised it was hard to find
NGitHub
Light LDAP implementation. Contribute to lldap/lldap development by creating an account on GitHub.
NWhich I realize is not linked from the main page, we link to the folder
NIn the "known compatible services" section
NCould I trouble you to create an issue to remind me to fix that? I might forget
NAnd now back to your problem, can you tell me what's wrong?
NHow do you run LLDAP? Docker? With a docker compose? In that case the address of the service is the name of the container (e.g. lldap, so http://lldap)
NI think you want all the containers in the same compose file
NI think the IP may not be stable on restarts
NAnd if you put them in the same compose (and same network or the default one) you don't have to expose the port to the internet
NIf you expose the port, then it's reachable at your IP
NIf it's blocked at the router level, then yes
NBut it's also possible to make it so only other docker services see the port
NI've just never heard of anyone using multiple compose files, that's it 