Simlified local-only/mixed setup (WAN/LAN)
After some discussion on zulip, I'd like to make a proposal how to improve the user experience for local-only and mixed deployments (services accessible from LAN/WAN).
The general idea is to serve services locally at http://[ip/hostname]/servicename
by default. If a service should be accessible from the internet, the current behavior will be enabled additionally.
This also adresses #312 (closed), #286
Goals / Benefits:
- improve user experience for deployments without a domain
-
keep services local only to reduce attack surface=> authelia -
expose selected services to the internet=> authelia - if a domain gets added, allow migration from local-only to public => also kind of authelia
Proposed changes
This is most likely incomplete, because I'm still not fully aware of all the inner workings of HLOS
- templates need to be updated to serve not only subdomains, but paths as well, something like mentioned below
What are your thoughts on this?
UPDATE (7.Jun.2020): This post has been modified to better reflect the current discussion: focus on simplified local setups
Edited by Buxel