Support PR / Community App Creation for ClearNet support to Advanced users

[tlindi]

Is your content request related to a problem? Please describe.
Configuration of Clearnet, ie for LNbits does need manual install of certbot tool and custom nginx conf(file).

Describe the solution you'd like
https_public_apps.conf is now commented out, and could be used as a base.

Support would need somewhere in WebUI setting for domainname and hostnames too, or optionally some configfile for advanced users to place settings on command line.

I'd like to create a PR and here I would like to hear how this could be created.

Additional context
I have such setup and someone was asking on Telegram how to publish LNbits to clearnet from MyNode, and I found zero instructions for such.

In case of device failure on my setup I'd need to do much of custom patching & googling, again.
Optionally documentation of setup could be a partial solution, before any software based solution.

• Mark this if you searched the existing list of open/closed issue and did not find anything similar

[tlindi]

Needed:

• Settings Page Chapter for "ClearNet / Domain"
• a) to enter FQDN(s) which is pointing to MyNode
• b) add remove FQDN(s) or hostnames to get certs
• c) "Renew now" focing button
• "My IP Address"-viewer to find out if ClearNet looks even to be possible in this setup (eg, users ISP device has not IP seen by IPChecker) (optionally)
• Per App nginx config file(s) (could reuse modified https_public_apps.conf )
• needed certbot / letsencrypt software installation
• incoming http-traffic tester to support certbot nginx based verification
• initial certification(s) fetching
• creation to crontab (or similar) to renew certs periodically

[tlindi]

FQDN for MyNode Apps can be set by creating file: /etc/nginx/mynode/https_domain.conf
with content
set $https_domain yourdomainname.tld;

And then https_public(_apps).conf can use that variable like this

server {
    include /etc/nginx/mynode/https_domain.conf;

    listen 6000 ssl;
    server_name $https_domain;
...