Support HTTPS when serving locally

[nuzzles]

For me, this is absolutely crucial because my web app checks cookies on startup, which must exist to continue the app.

Cookies are very special, and can only be retrieved on the same domain with Javascript/wasm bindings.

Hence, I need to serve my application with self-signed certs.

This is my typical workflow:

Create an /etc/hosts entry:

127.0.0.1   localhost.mydomain.com

Create local certs:

brew install mkcert
brew install nss
mkcert -install
mkcert -key-file ~/.cert/mydomain-key.pem -cert-file ~/.cert/mydomain-cert.pem localhost.mydomain.com

Then, I serve with Trunk:

[serve]
addresses = ["127.0.0.1"]
port = 3000
aliases = ["https://localhost.mydomain.com"]
ws_protocol = "wss"
tls_key_path = "~/.cert/mydomain-key.pem"
tls_cert_path = "~/.cert/mydomain-cert.pem"

This would serve on https://localhost.mydomain.com:3000, and hence my bevy app can load cookies properly for the .mydomain.com path

[nuzzles]

I would add, this issue is absolutely a blocker for my personal adoption since I see no way to run my app properly otherwise.

[NickTheFox99]

I would recommend using bevy build web --bundle and serving the build directory directly yourself, as bevy run web is only really used for testing locally afaik and should not be used in production anyways.

[nuzzles]

I am not looking for production optimization, but I do think serving with https is a common dev action and necessary for some people, such as myself, to properly test cookies.