https without a reverse proxy

[laralove143]

by default the app just runs an http server and we need a reverse proxy like nginx or a tunnel to terminate ssl. it would be cool if this was done at an app-level for us, as a reverse proxy just for this might be overkill

not sure if the used http/ws server library supports https upgrades but if it does, it should be as simple as providing the cert path in config.json

thank you for the app! me and my friends love it

[RblSb]

You can check if new config options works for you (sslKeyPemPath and sslCertPemPath absolute file paths)

[laralove143]

yayy it workss! thank u so much!

2 nits, maybe u dont agree w them cos including them in default-config.json could suffice, if so just close this:

1. should probably document all this, including how to set port to 443 for https (sudo setcap CAP_NET_BIND_SERVICE=+eip $(which node)

2. putting in the ip shows:

curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above

but putting in the domain for it (i set up A synctube {ip} Proxied on cf) works, probably expected but could be documented (got certs from cf)