I'm running rap + rancher on my homeserver, but I don't want to make every web application accessible from the outside via a FQDN. An example: I'm running a ympd instance to controll my Music Player Daemon. Since the music is only played at home, I don't want to have a publicly available URL, e.g. ympd.example.com, to access the web interface, because I'd then have to e.g. password protect it to prevent missuse. Instead, I'd like to make use of .local in order to get a local domain in my LAN, e.g. ympd.local, which would then automatically be resolved to the local LAN IP of the nginx proxy, which itself proxies the request to the host in my cluster running the ympd instance.
From a configuration perspective, I imagine one could just use the rap.host label and set it to ympd.local, which would then configure the nginx proxy to forward any connections to ympd.local to the rancher host running the ympd instance.
The way I understand it, rap would just have to add an avahi daemon plus some more advance parsing of the rap.host variable to its container being able to broadcast several .local domains. In some cases one might even define publicly available domains in addition to local domains, i.e. to circumvent password protection for local access from within the LAN, e.g. via rap.host=ympd.example.com,ympd.local, but that would just be a nice-to-have.
sesceu
commented
7 years ago
I'm running rap + rancher on my homeserver, but I don't want to make every web application accessible from the outside via a FQDN. An example: I'm running a ympd instance to controll my Music Player Daemon. Since the music is only played at home, I don't want to have a publicly available URL, e.g. ympd.example.com, to access the web interface, because I'd then have to e.g. password protect it to prevent missuse. Instead, I'd like to make use of .local in order to get a local domain in my LAN, e.g. ympd.local, which would then automatically be resolved to the local LAN IP of the nginx proxy, which itself proxies the request to the host in my cluster running the ympd instance.
From a configuration perspective, I imagine one could just use the rap.host label and set it to ympd.local, which would then configure the nginx proxy to forward any connections to ympd.local to the rancher host running the ympd instance.
The way I understand it, rap would just have to add an avahi daemon plus some more advance parsing of the rap.host variable to its container being able to broadcast several .local domains. In some cases one might even define publicly available domains in addition to local domains, i.e. to circumvent password protection for local access from within the LAN, e.g. via rap.host=ympd.example.com,ympd.local, but that would just be a nice-to-have.
Is something like this possible/planned?