The share button on a site currently only starts the LAN proxy. The CLI already goes further, lerd share tunnels a site through ngrok, cloudflared, expose, serveo or localhost.run, auto-picking whichever tool is installed, but none of that is reachable from the web UI.
The share control should grow into a small menu: share on LAN as today, plus a public tunnel entry per supported tool, with the same auto pick as the default choice. Tools that are not installed on the machine show up disabled with a hint about installing them. Starting a tunnel from the UI means lerd-ui owns the tunnel process, waits for the tool to print its public URL, shows that URL next to the site the way the LAN link is shown, and offers a stop action. Unlike the LAN proxy, a tunnel started from the UI should not be resurrected on restart, it ends when stopped or when lerd-ui shuts down.
The share button on a site currently only starts the LAN proxy. The CLI already goes further, lerd share tunnels a site through ngrok, cloudflared, expose, serveo or localhost.run, auto-picking whichever tool is installed, but none of that is reachable from the web UI.
The share control should grow into a small menu: share on LAN as today, plus a public tunnel entry per supported tool, with the same auto pick as the default choice. Tools that are not installed on the machine show up disabled with a hint about installing them. Starting a tunnel from the UI means lerd-ui owns the tunnel process, waits for the tool to print its public URL, shows that URL next to the site the way the LAN link is shown, and offers a stop action. Unlike the LAN proxy, a tunnel started from the UI should not be resurrected on restart, it ends when stopped or when lerd-ui shuts down.