tunwg.com, as data

To use your own domain name instead of a subdomain on tunwg.com, add a CNAME record in your DNS provider to the encoded domain on tunwg.com e.g. for `test.example.com`, add a CNAME entry for `test` to `xxxxxxxx.l.tunwg.com`### Use directly in Go programsIf you're writing your HTTP server in golang, you can use `tunwg` directly without running a separate binary.import "github.com/ntnj/tunwg"listener, err := tunwg.NewListener("<name>")http.Serve(listener, httpHandler)### Persistent URLsSince the generated subdomain is derived from your wireguard key and the forwarded address, it'll remain constant across process restarts. The wireguard key is stored in `.config/tunwg/` (os.UserConfigDir/tunwg) or `/data/` in docker. It can be customized with `TUNWG_PATH` environment variable.### Automatic SSL certificatesAutomatic SSL certificate are issued through LetsEncrypt and automatically renewed. Fallback to ZeroSSL is supported in case of LetsEncrypt rate limits.### Relay traffic over HTTPSIn case your firewall blocks UDP packets, you can relay the traffic over HTTPS. To use, just add `TUNWG_RELAY=true` to client environment variables.This will effectively be TCP over UDP over TCP, so performance will suffer in case of packet drops. Use this option only if needed.### Expose ports on other hostsYou can forward any ports on local network which the machine running tunwg has access to, without installing tunwg on the forwarded host. e.g.tunwg --forward=http://10.0.0.2:8000,http://10.0.0.10:9000This is especially useful when running `tunwg` with docker compose to expose the ports on other containers without making any modifications to those images. e.g. `docker-compose.yml`command: tunwg --forward=http://whoamiYou can then run `docker compose logs tunwg` to view the generated URL.### HTTP Basic Auth supportTo expose private servers using tunwg, you can use the inbuilt basic auth support.