enable HTTPS without reverse proxy

[fanyangto]

What type of request is this?

Enhancement of an existing feature

Clear and concise description of the feature you are proposing

I am generally familiar with openssl and PKI operations to create server certs. Is there a way/documentation on how to enable HTTPS on Enclosed app without putting a reverse proxy in front of it ? I find the documentation lacking in this regard. We probably need a few pointers on how to do this, and we can run along on our own.

Ideally, the Enclose app should support HTTPS on its own, with the cert/keystore passed in to the docker environment. It could even deploy a self-signed cert, until the user has the time to replace it with a proper cert chain.

This would be so much better than upon the first docker deployment, the page is basically unusable due to the lack of HTTPS.

Additional context

No response

Validations

• Check the feature is not already implemented in the project.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
• Check that the feature is technically feasible and aligns with the project's goals.

[CorentinTh]

Hey @fanyangto

Just added native HTTPS support in #376 with either cert + key or pfx + passphrase
It's available for enclosed version >= 1.14

You can see the added configuration variable in the config page, and a dedicated explanation here: https://docs.enclosed.cc/self-hosting/configuration#optional-native-https-configuration